Getting a java Runtime error on devices with emulated external storage. Please help!

Solar2D Android
#1

Hey everybody!

I have been getting several crash reports from Google Play customers who have “emulated” exernal storage on their devices.

This prevents the .obb file from being downloaded to their device and causing the crash.

is there something (hopefully!) that I can add to the build settings to correct this?

Or something I can tell them to do on their device to clear out the issue?

It seems to be fairly common as I have already received six emails from different people who are having this problem.

Attached is a screenshot of what the crash looks like.

And here is the crash report:

java.lang.RuntimeException: java.lang.IllegalArgumentException: Invalid path: /storage/emulated/0
Java Stack Trace:
android.os.StatFs.doStat(StatFs.java:46)
android.os.StatFs.<init>(StatFs.java:39)
CoronaProvider.licensing.google.LuaLoader$GetAvailableExternalSpaceWrapper.invoke(LuaLoader.java:493)
com.ansca.corona.JavaToNativeShim.nativeTouchEvent(Native Method)
com.ansca.corona.JavaToNativeShim.touchEvent(JavaToNativeShim.java:282)
com.ansca.corona.input.RaiseTouchEventTask.executeUsing(RaiseTouchEventTask.java:39)
com.ansca.corona.CoronaRuntimeTaskDispatcher$TaskEvent.Send(CoronaRuntimeTaskDispatcher.java:153)
com.ansca.corona.events.EventManager.sendEvents(EventManager.java:229)
com.ansca.corona.Controller.updateRuntimeState(Controller.java:223)
com.ansca.corona.opengl.CoronaGLSurfaceView$CoronaRenderer.onDrawFrame(CoronaGLSurfaceView.java:399)
com.ansca.corona.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1622)
com.ansca.corona.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1377)
stack traceback:
[C]: ?
[C]: in function ‘getAvailableExternalSpace’
?: in function ‘?’
?: in function ‘?’
?: in function ‘_onEvent’
?: in function ‘?’
?: in function <?:1056>
?: in function <?:218>

Any help is appreciated!

Joe

#2

Hi,

We’ve tried reproducing this issue on all the devices which we have but couldn’t make it happen.  Could you reproduce this issue yourself?  Do you know what devices that it happens on?  Is there any other information you can give us?

We did make a change based on the stack trace you gave us which MIGHT resolve the issue we can’t be 100% sure of that.

#3

Was there ever an update to this? Would like to avoid this error on future titles should there be something about this error that is not specific to Fire Maple Games.

Thanks

#4

We couldn’t reproduce this problem on any of our devices but based on the stack trace that was provided we did try to put in a work around.  We can’t be sure this will completely solve the issue since we couldn’t recreate the issue.

#5

Hi,

We’ve tried reproducing this issue on all the devices which we have but couldn’t make it happen.  Could you reproduce this issue yourself?  Do you know what devices that it happens on?  Is there any other information you can give us?

We did make a change based on the stack trace you gave us which MIGHT resolve the issue we can’t be 100% sure of that.

#6

Was there ever an update to this? Would like to avoid this error on future titles should there be something about this error that is not specific to Fire Maple Games.

Thanks

#7

We couldn’t reproduce this problem on any of our devices but based on the stack trace that was provided we did try to put in a work around.  We can’t be sure this will completely solve the issue since we couldn’t recreate the issue.