• Clearing of Chat Logs
    We're planning to clear chat logs very soon, this is to help clear up server space as a routine maintenance for DomiNations. Please take this time to save any important chat messages before they're gone.

Nexus 6P :: Marshmallow Immediate Crash

W

WhyteFyre

Approved user
Joined
Aug 27, 2015
Messages
7
Hello and to whom it may concern,
As the title suggests, I am having an issue with stock android on the Nexus 6P. DomiNations immediately crashes upon launching the game. No permissions are being asked, which is leaning towards something not being set properly. I haven't rooted either. My Note 4, OnePlus One, and Galaxy S3 launch the game properly.

Regards,
-WhyteFyre
 
Sort by date Sort by votes
Kid G

Kid G

Approved user
Joined
Dec 3, 2015
Messages
15
I'm having the exact same issue on my Nexus 7 running stock Android Marshmallow. (I posted the issue in this forum yesterday).

I also tried out the new release on an iPhone 6S and Samsung Galaxy Grand Prime. Neither of which had any issues. I've tried every remedy that Nexon has suggested but without any luck. I had been considering resetting my tablet to factory defaults and trying again. However, if this is a problem related to stock Android, I wouldn't expect a different outcome.

I'll let everyone know if this gets resolved. I would appreciate the same feedback.

Kid G
 
Upvote 0 Downvote
W

WhyteFyre

Approved user
Joined
Aug 27, 2015
Messages
7
Kid G said:
I'm having the exact same issue on my Nexus 7 running stock Android Marshmallow. (I posted the issue in this forum yesterday).

I also tried out the new release on an iPhone 6S and Samsung Galaxy Grand Prime. Neither of which had any issues. I've tried every remedy that Nexon has suggested but without any luck. I had been considering resetting my tablet to factory defaults and trying again. However, if this is a problem related to stock Android, I wouldn't expect a different outcome.

I'll let everyone know if this gets resolved. I would appreciate the same feedback.

Kid G
Click to expand...
Thanks for confirming. I'll have to adb it tonight, in hopes of finding out the function call the app is failing on. I'll provide a more complete response when I find it out.
 
Upvote 0 Downvote
Kid G

Kid G

Approved user
Joined
Dec 3, 2015
Messages
15
Sounds good. I may end up trying a factory reset even though I don't expect a resolution.

I had a similar (yet unrelated) issue with the last update in which Nexon had added anti-hacking checks. I had no hacking utils installed nor was my tablet rooted. Nevertheless, I would constantly get booted from the game. I ended up uninstalling every game and app that I either never or rarely used. That approach resolved the particular issue but I never did discover the culprit.

I'm beginning to feel that Nexon needs to add a stock Android device to their testing bed...

Kid G
 
Upvote 0 Downvote
W

WhyteFyre

Approved user
Joined
Aug 27, 2015
Messages
7
Found out the issue. Connecting the phone to the computer and running logcat after setting up adb and related system drivers, I was able to resolve the immediate crash upon startup.
Here's part of the logcat:

12-03 20:58:55.932 12946 12946 W ResourceType: Invalid package identifier when g
etting bag for resource number 0x00000000
12-03 20:58:55.944 12946 12946 I Prime31 : found Activity proxy class: class com
.prime31.GoogleCloudMessagingPlugin
12-03 20:58:55.944 12946 12946 I Prime31 : found Activity proxy class: class com
.prime31.PlayGameServicesPlugin
12-03 20:58:55.945 12946 12946 I Prime31 : onCreate. calling through to init
12-03 20:58:55.985 12946 12946 W PopupManager: You have not specified a View to
use as content view for popups. Falling back to the Activity content view which
may not work properly in future versions of the API. Use setViewForPopups() to s
et your content view.
12-03 20:58:56.331 12946 12946 D AndroidRuntime: Shutting down VM
12-03 20:58:56.334 12946 12946 E AndroidRuntime: FATAL EXCEPTION: main
12-03 20:58:56.334 12946 12946 E AndroidRuntime: Process: com.nexonm.dominations
.adk, PID: 12946
12-03 20:58:56.334 12946 12946 E AndroidRuntime: java.lang.Error: FATAL EXCEPTIO
N [main]
12-03 20:58:56.334 12946 12946 E AndroidRuntime: Unity version : 4.6.7p1
12-03 20:58:56.334 12946 12946 E AndroidRuntime: Device model : Huawei Nexu
s 6P
12-03 20:58:56.334 12946 12946 E AndroidRuntime: Device fingerprint: google/angl
er/angler:6.0/MDB08L/2343525:user/release-keys
12-03 20:58:56.334 12946 12946 E AndroidRuntime:
12-03 20:58:56.334 12946 12946 E AndroidRuntime: Caused by: java.lang.RuntimeExc
eption: Unable to start activity ComponentInfo{com.nexonm.dominations.adk/com.ne
xon.dominations.MainActivity}: java.lang.SecurityException: getDeviceId: Neither
user 10119 nor current process has android.permission.READ_PHONE_STATE.
12-03 20:58:56.334 12946 12946 E AndroidRuntime: at android.app.ActivityT
hread.performLaunchActivity(ActivityThread.java:24 16)
12-03 20:58:56.334 12946 12946 E AndroidRuntime: at android.app.ActivityT
hread.handleLaunchActivity(ActivityThread.java:247 6)
12-03 20:58:56.334 12946 12946 E AndroidRuntime: at android.app.ActivityT
hread.-wrap11(ActivityThread.java)
12-03 20:58:56.334 12946 12946 E AndroidRuntime: at android.app.ActivityT
hread$H.handleMessage(ActivityThread.java:1344)
12-03 20:58:56.334 12946 12946 E AndroidRuntime: at android.os.Handler.di
spatchMessage(Handler.java:102)
12-03 20:58:56.334 12946 12946 E AndroidRuntime: at android.os.Looper.loo
p(Looper.java:148)
12-03 20:58:56.334 12946 12946 E AndroidRuntime: at android.app.ActivityT
hread.main(ActivityThread.java:5417)
12-03 20:58:56.334 12946 12946 E AndroidRuntime: at java.lang.reflect.Met
hod.invoke(Native Method)
12-03 20:58:56.334 12946 12946 E AndroidRuntime: at com.android.internal.
os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.j ava:726)
12-03 20:58:56.334 12946 12946 E AndroidRuntime: at com.android.internal.
os.ZygoteInit.main(ZygoteInit.java:616)

:: TL;DR ::
READ_PHONE_STATE permission was not given to the app, hence the crash.

In Marshmallow, set the app's permissions via
1. Settings > Apps > DomiNations > Permissions
2. There are three individual permissions Contacts, Phone, and Storage.
3. Allow all three.
4. Launch the game and connect your Google Play profile
5. Profit and have fun playing it.
6. To the game devs, if you need an outside tester, I'll be available :p
I'm a programmer and familiar with all this. A normal user with a high-end phone shouldn't go through hoops like I did.
 
Last edited:
Upvote 0 Downvote
Kid G

Kid G

Approved user
Joined
Dec 3, 2015
Messages
15
Thank you so much for putting in more time than Nexon to solve this. :)

If you don't mind, I'll link this post to my support thread with them.

Again, I really appreciate the help.

Kid G
 
Upvote 0 Downvote
G

Guest

Guest
Thanks for that workaround WhyteFyre! I've made a sticky post in this section so that more marshmallow users can find the workaround. We are also looking into a more permanent solution. Appreciate the reports everyone has sent in!
 
Upvote 0 Downvote
W

WhyteFyre

Approved user
Joined
Aug 27, 2015
Messages
7
Seraphine said:
Thanks for that workaround WhyteFyre! I've made a sticky post in this section so that more marshmallow users can find the workaround. We are also looking into a more permanent solution. Appreciate the reports everyone has sent in!
Click to expand...
Thanks for making a sticky thread on it. Hope it proves useful for the other players that are on Marshmallow. This game is fun to unwind after a hectic work day. Glad I could help :)
 
Upvote 0 Downvote
You must log in or register to reply here.
Top