"the connection to the server was unsuccessful file ///android_asset/www/index.html"

Hi Guys,

I use ZM 1.30.4 and zmninja 1.2.504.

From several days when i run zmninja i get this message:
"the connection to the server was unsuccessful file ///android_asset/www/index.html"

and the app doesn't want to continue. I have to kill the process in System Menu of Android to normaly run zmninja again.

I saw some posts about this message but still don't have any solution.

Can you help ?

Thanks !

Eric

[pliablepixels]

Please post more details:

1. mobile OS version
2. Device name
   3 When exactly does this occur - only when you exit the app from the "Exit" button in the app ?
3. What if you kill the app from task bar?
4. Which post did you see? Please post a link

Hi
Mobile is a Sony Xperia running Android 6.0.
Problem occurs even if i push the Exit button or if come back to Android with the back function. Killing zmninja From the task bar works. I can then use zmninja normaly.
Thanks for your help

[pliablepixels]

I've emailed you a new apk - please see if that helps with the "back button" problem (please don't use exit from menu)

You will have to delete the existing app

Hi, Thank you. I don't have the "connexion ..." error message anymore but Zmninja hangs and stay on the logo entry. I've to kill it like before if i want to run it normally. Eric 2017-10-10 15:29 GMT+02:00 Pliable Pixels <notifications@github.com>:

…

I've emailed you a new apk - please see if that helps with the "back button" problem (please don't use exit from menu) You will have to delete the existing app — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/pliablepixels/zmNinja/issues/550#issuecomment-335472438>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ab7H9__MII8Ofd6iFS4aA-PWBqDze_-fks5sq3EvgaJpZM4PzBgk> .

i finally get the same error message but this message takes a more longer time to come on the screen. Did you add a timeout ? Eric 2017-10-10 15:29 GMT+02:00 Pliable Pixels <notifications@github.com>:

…

I've emailed you a new apk - please see if that helps with the "back button" problem (please don't use exit from menu) You will have to delete the existing app — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/pliablepixels/zmNinja/issues/550#issuecomment-335472438>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ab7H9__MII8Ofd6iFS4aA-PWBqDze_-fks5sq3EvgaJpZM4PzBgk> .

[pliablepixels]

Yes, so it looks like the shortage of time was not the issue. At this stage, I have no idea to be honest - I can't replicate this issue on any of my android devices. Are you seeing this issue on any other android device?

I can reproduce this error as well by selecting exit from the app or by using the back button to exit.
This is on a Moto Z2 play running Android 7.1.1 and zmNinja-pro v1.2.504. FWIW, I installed zmNinja-pro or two other android devices to see what they did, one running 4.4.4 and one running 6.0.1 and could not replicate this problem. However, on the device running 6.0.1 hitting the back button always caused the app to crash when it exits. All are running Chrome 61.0.3163.98 so I don't guess that's it. Killing the app through the recent apps screen or killing it manually with the kill command would allow me to bring it back up again. I never exit the app usually anyway so it's not a big deal at all to me really!!

[radeon79]

I have the same problem. My phone is oneplus 3t with stock firmware Nougat.
Please fix soon....

Please try this : - With a good wifi/wan bandwidth - With a low bandwith like h+ Ans give us the results. Le 28 oct. 2017 10:02, "radeon79" <notifications@github.com> a écrit :

…

I have the same problem. My phone is oneplus 3t with stock firmware Nougat. Please fix soon.... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/pliablepixels/zmNinja/issues/550#issuecomment-340158299>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ab7H9xfZwipRmTfVWyISHJlrvWPieUeBks5swt-vgaJpZM4PzBgk> .

[davidbetter]

Hi,

Got the exact same problem. Running Android 7 on a Samsung Galaxy A5 2017.
Installed the app yesterday (1.2.504) and this is a bit annoying to be honest..

Would be great to get a resolution!
Great app otherwise...

[davidbetter]

Hmm... I think I might have found a work around / solution.
In the Appinfo meny (where you can kill the App) there is a menu for permissions.
I gave the zmNinja access to the storage.
That was it for me. Now it works like a charm.

Good luck!

[pliablepixels]

Can The others please test @davidbetter’s solution? Thanks for investigating. None of my devices exhibit this issue and I have no way of zeroing in.

This solves the problem for me as well!

[pliablepixels]

I looked at the permissions the app requests when installed. They are:

uses-permission: name='android.permission.INTERNET'
uses-permission: name='android.permission.ACCESS_NETWORK_STATE'
uses-permission: name='android.permission.WRITE_EXTERNAL_STORAGE'
uses-permission: name='android.permission.READ_EXTERNAL_STORAGE'
uses-permission: name='android.permission.MANAGE_DOCUMENTS'
uses-permission: name='android.permission.WAKE_LOCK'
uses-permission: name='android.permission.VIBRATE'
uses-permission: name='com.google.android.c2dm.permission.RECEIVE'
uses-permission: name='com.pliablepixels.zmninja_pro.permission.C2D_MESSAGE'
uses-permission: name='com.pliablepixels.zmninja_pro.permission.PushHandlerActivity'
permission: com.pliablepixels.zmninja_pro.permission.C2D_MESSAGE
permission: com.pliablepixels.zmninja_pro.permission.PushHandlerActivity
uses-permission: name='com.sec.android.provider.badge.permission.READ'
uses-permission: name='com.sec.android.provider.badge.permission.WRITE'
uses-permission: name='com.htc.launcher.permission.READ_SETTINGS'
uses-permission: name='com.htc.launcher.permission.UPDATE_SHORTCUT'
uses-permission: name='com.sonyericsson.home.permission.BROADCAST_BADGE'
uses-permission: name='com.sonymobile.home.permission.PROVIDER_INSERT_BADGE'
uses-permission: name='com.anddoes.launcher.permission.UPDATE_COUNT'
uses-permission: name='com.majeur.launcher.permission.UPDATE_BADGE'
uses-permission: name='com.huawei.android.launcher.permission.CHANGE_BADGE'
uses-permission: name='com.huawei.android.launcher.permission.READ_SETTINGS'
uses-permission: name='com.huawei.android.launcher.permission.WRITE_SETTINGS'
uses-permission: name='android.permission.READ_APP_BADGE'
uses-permission: name='com.oppo.launcher.permission.READ_SETTINGS'
uses-permission: name='com.oppo.launcher.permission.WRITE_SETTINGS'

Both READ and WRITE of External Storage is there.

Looking at the Android permissions page here I don't see any other permissions related to storage.

Can anyone who has some idea of Android enlighten me ? What is this storage option in App info ? I'm an iOS guy.

I'm far from an Android expert, but I think here is the key parts:

"
If the device is running Android 6.0 (API level 23) or higher, and the app's targetSdkVersion is 23 or higher, the app requests permissions from the user at run-time. The user can revoke the permissions at any time, so the app needs to check whether it has the permissions every time it accesses permission-protected APIs. For more information about requesting permissions in your app, see the Working with System Permissions training guide.
If the device is running Android 5.1.1 (API level 22) or lower, or the app's targetSdkVersion is 22 or lower, the system asks the user to grant the permissions when the user installs the app. If you add a new permission to an updated version of the app, the system asks the user to grant that permission when the user updates the app. Once the user installs the app, the only way they can revoke the permission is by uninstalling the app.
"

So basically anyone running API Level 23 or higher needs to be prompted to allow the storage permissions to be given. On the older Android versions, this is automatically set as the user agrees to this when they install it from the play store. On my 4.4.4 device for example, I can list the permissions the app has, but can't change them as they are permanently enabled . So I think if you could add a prompt to request storage permission for versions 6.0 or higher of Android this would fix the problem.