When you want to test your Twixl Publisher publication on Android on your own devices, we provide different options to do that.
1. Preview on a device
Preview on a device is the quickest way to get content on your tablet, and allows you to push the publication contents from the plug-in to the Twixl Viewer app.
More details are available in this article.
2. Single-file Android test build via the SD card
This method will allow you to install the whole app and its contents as a single .apk file.
Start by creating the test build of your app. The result will be a folder containing a file with the extension .apk (e.g. main.10000.com.twixlmedia.mymagazine.apk). The package name will be based on the Android Application ID you defined in the Build Settings.
- Copy the installation file (.apk) to the SD Card (any location will do as this is only an installation file). If you are on a Windows computer, there is no additional installation needed to copy files to the SD Card of the tablet.
- After you copied that file to the SD Card, use a tool like ES File Explorer or File Manager on your tablet to navigate to the contents on that SD Card. Now open the installation .apk file to launch the publication.
If you're on macOS (OS X), you can use 2 tools to copy files to your Android device:
Although this method may be a quicker way to test your app, it’s always good practice to test a Google Play build according to the method below before submitting your final app to the Google Play store.
3. Testing a Google Play build via SD card installation
When you build your Twixl Publisher publication for Google Play, the output will consist of 2 files: a file with extension
.apk and a second one with extension
.apk: This is the application installation file.
.obb: This contains the Twixl publication itself.
Putting the application and the .obb file on the SD Card will provide a similar experience to when a user starts the application for the first time after downloading it from the Google Play store. The .obb file needs to be placed at the following location in order for the app to function properly: