Moodle Mobile Building Automatic Building System: Difference between revisions
Juan Leyva (talk | contribs) (Created page with "1 Build the .apk file using the Android SDK with all the plugins we need (WebIntent, Notificacions, Childbrowser, etc..) 2 Use this apk as a template for future builds 3 Make an ...") |
Juan Leyva (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
== Introduction == | |||
== Requirements == | |||
== Steps == | |||
1 Build the .apk file using the Android SDK with all the plugins we need (WebIntent, Notificacions, Childbrowser, etc..) | 1 Build the .apk file using the Android SDK with all the plugins we need (WebIntent, Notificacions, Childbrowser, etc..) | ||
2 Use this apk as a template for future builds | 2 Use this apk as a template for future builds | ||
3 Make an automatic build process that does something like (can be a cron job) | 3 Make an automatic build process that does something like (can be a cron job) | ||
Extract our .apk file template in a directory (apktool d path/to/yourApp.apk path/to/output-folder) | Extract our .apk file template in a directory (apktool d path/to/yourApp.apk path/to/output-folder) | ||
Download from moodlehq/moodlemobile repository the last files to -> apkdirectory/assets/www directory (where all the html, css, js files are stored) | Download from moodlehq/moodlemobile repository the last files to -> apkdirectory/assets/www directory (where all the html, css, js files are stored) | ||
Re-build the .apk file (apktool b path/to/output-folder path/to/yourAppV2.apk ) | Re-build the .apk file (apktool b path/to/output-folder path/to/yourAppV2.apk ) | ||
Re-sign the .apk file (jarsigner -verbose -keystore ~/.android/debug.keystore path/to/yourAppV2.apk androiddebugkey) | Re-sign the .apk file (jarsigner -verbose -keystore ~/.android/debug.keystore path/to/yourAppV2.apk androiddebugkey) |
Latest revision as of 14:16, 20 March 2013
Introduction
Requirements
Steps
1 Build the .apk file using the Android SDK with all the plugins we need (WebIntent, Notificacions, Childbrowser, etc..)
2 Use this apk as a template for future builds
3 Make an automatic build process that does something like (can be a cron job)
Extract our .apk file template in a directory (apktool d path/to/yourApp.apk path/to/output-folder)
Download from moodlehq/moodlemobile repository the last files to -> apkdirectory/assets/www directory (where all the html, css, js files are stored)
Re-build the .apk file (apktool b path/to/output-folder path/to/yourAppV2.apk )
Re-sign the .apk file (jarsigner -verbose -keystore ~/.android/debug.keystore path/to/yourAppV2.apk androiddebugkey)