Extra’s you need to build an .apk (this is Android’s .exe)
- Download Android studio here: https://developer.android.com/studio/
- Run Android Studio (it is very slow to open)
- From there you can check out your built .apk
- Run a bug report
- Update your sdk to the latest versions (Tools – SDK Manager)
- And much more. A user guide is here: https://developer.android.com/studio/intro
A log report tells you what your phone is doing every step of the way. If you report an Android error it is helpful (vital) to Clickteam if you include a log report.
Step 1 is to switch your phone to developer mode:
Under settings there will be a build number – tap that 7 times.
Step 2 is to navigate to settings – developer options on your phone. Many of them have the reports and what you need integrated into the phone and you can get that from there.
If your phone does not have the reports integrated there are several ways you can do it:
1. Use Android Studio
2. Use Adb – directly with USB cable by typing in the commands from the command prompt
3. Use Adb with a number of apps from Google Play that generate these reports
How to setup ADB:
- Download sdk tools from here: https://developer.android.com/studio...orm-tools.html
- Extract it to somewhere on your computer – preferably something with a simple name like c:\adb
- Press windows key + r
- Type in cmd
- Type in cd ..
- Type in cd\adb (or whatever you named your directory)
- Type adb.exe
- Now adb is ready to run.
- Connect your cell phone via usb cable – make sure that debugging mode is enabled and that your cell phone is NOT connected as a media device – play around with your settings there if this doesn’t work – different phones call the connections different things.
- To see if your phone is connected: from the command prompt type: adb devices
- A list of your devices should appear, and your device might ask for permission that you need to grant.
- Your device is likely to be identified by a string of numbers.
- From this point if you use an app from Google Play store they will give you a command to type here and then generate the report with the app and email it to you.
- Else type: adb logcat -d > logcat.txt
- Go to your phone and run the Fusion App and the .txt file will be updated with your log which you will find in the directory that you’re running from.
- Type exit to close the command prompt box – or close it from the X
- Some cell phones and older tablets will pop-up the navigation bar over the game. There are 2 ways to overcome this.
- Choose the option under Android properties for your game to Display status bar
- Don’t choose that option but instead using the Android or Android + objects set Immersive mode to ON
- Note that immersive mode doesn’t work on some old tables (early Android versions) – your best option is to display the status bar there.
- The Android object allows you to:
- To hide/ show action / title bar / status bar / navigation bar
- The Android+ object (Fusion Developer) allows you to:
- Test if the device is a tablet
- Set layout to follow the phone for example Set layout to Landscape (sensor:1)
- Android doesn’t automatically include external files in your build – for example with Active Picture.
- You are required to add these in yourself by adding them into Binary Data
- Click the icon with the music note / paper next to the frame number name at the top of your screen – navigate to Binary Data – add them in there.
Here you can also find a list of extensions – when you report an issue in Android – take a screenshot of these extensions and include that as well.
- Certain devices have sound issues.
- Keep your sounds equal to or below 192kbps for Huawei compatibility
- Playing a sample more than once will not work on old devices – on some of them you can make it work by selecting the option: play from disk (This is an option when you import the sound.)
- Alternatively repeat the command that plays them once or repeat the sounds in a sound editor and import it into Fusion as a single sound.
Not everything that works in Windows Fusion works in Android
- A lot of the info in the manual is out of date.
- However, it’s important to note that effects won’t work in Android:
- Active object – set effect doesn’t work
- Transition effects don’t work
- Alpha-blending does work
The information under Android Properties is useful but note the following:
- If you’re publishing on Google Play then:
- Your minimum target version should be the lowest version you or Fusion will allow your game / app to work on.
- Your Target Android version should be the maximum version you can select at that moment.
If you want to test your device or any .apk on your phone that isn’t signed then turn off Google Play Protect – because it will block you from doing this – look under your phone for Security & Privacy and then look for Google Play and Protect
APK or AAB
- Currently you can create a .apk that you can install and test on your phone.
- You can also create an App Bundle known as an AAB for use on Google Play. This bundle allows the user to install only that which their phone needs. Using this now is optional on Google Play and they require you to allow them to sign / keep your keystore certificate. Note that this also gives them the power to revoke it – in which case the Google Play Protect will disable your apps.
Using OpenGL ES 3.0 will test your device to find which OpenGL version it has from 3.0 and under and then allocate that one. When you publish your app on Google Play you’ll see OpenGL ES 1.0+ as which display mode.
Family Friendly Apps on Google Play
If you now publish an app on the Family Friendly section, Google Play reviews it and approves it. This process can take several hours up to a week. Keep this in mind if you’re planning any kind of release promotion.
Enable object Load on Call options – is a product of 2.5+ - although it appears as an option on the version without 2.5 only until you save – then it disappears.