Unity Ads crashing iOS in 5.2 ?

Unity Services
1

Hello,

Has anyone else experienced crashing in iOS builds when migrating from 5.1 / Asset package to the integrated Ads in 5.2? We’ve removed the old Unity Ads asset from our project and activated the service within the editor. It seems to be linked up to our account correctly - we don’t see any errors within Unity.

However, when we build the project, we get a crash on launch. This appears to be where its erroring in XCODE:

xpets`il2cpp::vm::Class::FromIl2CppType:
    0x1019c6938 <+0>:   stp    x20, x19, [sp, #-32]!
    0x1019c693c <+4>:   stp    x29, x30, [sp, #16]
    0x1019c6940 <+8>:   add    x29, sp, #16
    0x1019c6944 <+12>:  mov    x19, x0
    0x1019c6948 <+16>:  movz   x0, #0
->  0x1019c694c <+20>:  ldrb   w8, [x19, #10]

When we turn off Ads -we are able to load into the game just fine. We will be filing a bug report this afternoon after a little more r&d.

2 Likes
2

We are not able to run 5.2 iOS builds either unless we turn Unity Ads off but we get a different error at runtime. We get EXC_BAD_ACCESS from vm::Method::GetParamCount.

3 Likes
3

After 5.2 update the game crash just after launch on iOS

4

Same problem here, it’s caused by trying to authenticate with game center with unity ads. I need a workaround =(

5

like mention in this thread as work around you can disable the unity ads in the services panel and instead import them as plugin from the asset store

6

I am facing same issue!
I am not using unity ads but the build crashes!

7

We are using Unity Ads. After upgrading to 5.2 i removed the plugin and tried to use the build-in solution (via the new services window). This was getting me a crash on vm::Method::GetParamCount.

When I disabled Unity Ads on the services tab and rolled back to the Unity Ads plugin everything started to work again.

Hope it helps you too.

8

FWIW, i had build errors in xcode after updating to integrated UnityAds in 5.2.
I removed the xcode folder and built back from Unity (instead of simply appending), and rebuilt in xcode, and it did work.

9

FYI, fixed in
5.2.1p3

10

Not fixed. I got same on 5.3.1p1

11

Same issue here in 5.3.5f1