Fatal Exception on iOS

[wave20...@gmail.com]

Hi  Teams

    We recently get a crash error for iOS, when playing the ad. The framework version is 3.13.0 

Fatal Exception: UIViewControllerHierarchyInconsistency

A view can only be associated with at most one view controller at a time! View <IMAWKWebView: 0x11e031100; frame = (0 0; 896 414); opaque = NO; autoresize = W+H; layer = <CALayer: 0x28074ed60>> is associated with <IMAWebUIViewController: 0x1088f8f00>. Clear this association before associating this view with <IMAWebUIViewController: 0x10886aee0>.

Your help would be much appreciated!

Thanks,

Haibo

[IMA SDK]

Hi there,

Thank you for bringing this issue to our attention.

I saw a couple issues reported to us which are also linked to UIViewControllerHierarchyInconsistency error. However, both of these cases are not related to the IMA SDK. Please note that UIViewControllerHierarchyInconsistency is not an IMA validation but instead an iOS UIKit/OS level (more information here).

Also, in case you are implementing full-screen solutions like juggling around the video views and view controllers. I’m afraid this is currently not explicitly supported by the IMA SDK. This implementation may also throw an error related to UIViewControllerHierarchyInconsistency.

Let me know if you have further questions or clarifications.


Regards,

Sherwin Diesta IMA SDK Team

 

ref:_00D1U1174p._5004Q2DuDR7:ref

[wave20...@gmail.com]

Hi  Teams

 

In our case, we only have the full-screen. so we do not change view controllers.  All the crash issues happened on the framework version  3.13.0.  Any other opinion would be appreciated.   

Thanks,

Haibo

[Interactive Media Ads SDK]

Reposting the last inquiry link from the forum as it wasn't routed to our support queue.

Cheers,

William Pescherine

IMA SDK Team

[IMA SDK]

Hi Haibo,

 

Thank you for your reply. How about using the latest SDK version (3.14.1) and see if you will encounter the same issue? Also, could you kindly share the following information so we can investigate on our end?

 

• VAST and VMAP ad tag (if client-side) / AssetKey or CMS and Video IDs (if DAI)
• Error encountered or complete stack trace if any
• Sample project file (if possible)

 

Kindly share the requested information to our testing alias: imate...@gmail.com

[IMA SDK]

Hi Haibo,

Thank you for your response.

I’m comparing the two crash logs you shared and these seem to be two different types of issue. Could you confirm if the previous one is still an issue, and the latest crash log is the current crash you are having? For the latest crash, what SDK version are you using here? Would it be possible for you to share with us the sample project file so we can check further?

Kindly send the project file privately to our testing alias: imate...@gmail.com


Regards,

[wave20...@gmail.com]

Hi Team 

   1, Both crashes are the same issue. please take a look at the following picture.

  2, Currently, the framework version we are using is 3.13.0.

  3, We can't provide a demo right now. And the frequency of errors is very low, we only can find it on the firebase crash report.

   

  4, We don't even know if the crash happened for vod or live.

Thanks,

Haibo

[IMA SDK]

Hi Wave,

Thank you for responding back to us about this issue. I work along with Sherwin and will be assisting you today. Having looked over the thread and the screenshots that you have sent us. If they are both dealing with the UIViewControllerHeirarchyInconsistanecy. As has been previously stated this is an iOS issue and when you read the logcat that you have in the screen as well as look at the screen you will see that it is due to more than one view as the child of the View Controller. the IMA SDK from what it looks like just sits inside of one of the Views.

If you would liek to share with us a simple sample app that displays this issue we will be happy to test against it and see if we find anything. But from what we can see. it is an iOS issue.

Regards,

William Pescherine IMA SDK Team

 

ref:_00D1U1174p._5004Q2DuDR7:ref

[Eric Douglass]

Based on the screenshot provided it looks like all classes involved are IMA controlled, "IMAWKWebView is associated with IMAWebUIViewController 0x11cc1b780, Clear this association before associating this view with IMAWebUIViewController 0x1062cf3a0." This does not look like an issue that consumers of the IMA SDK can fix on our side.

[IMA SDK]

Hi Eric,

I work with William and will assist you.

For better privacy I am reposting deleted posts without the ad tags:

Crashed: com.google.firebase.crashlytics.ios.exception
0  UnivisionNowSwift              0x104a2e2d4 FIRCLSProcessRecordAllThreads + 4373095124
1  UnivisionNowSwift              0x104a2e6b8 FIRCLSProcessRecordAllThreads + 4373096120
2  UnivisionNowSwift              0x104a24e54 FIRCLSHandler + 4373057108
3  UnivisionNowSwift              0x104a20a74 __FIRCLSExceptionRecord_block_invoke + 4373039732
4  libdispatch.dylib              0x194f6ddb0 _dispatch_client_callout + 20
5  libdispatch.dylib              0x194f7c428 _dispatch_lane_barrier_sync_invoke_and_complete + 60
6  UnivisionNowSwift              0x104a2020c FIRCLSExceptionRecord + 4373037580
7  UnivisionNowSwift              0x104a20504 FIRCLSExceptionRecordNSException + 4373038340
8  UnivisionNowSwift              0x104a1fdec FIRCLSTerminateHandler() + 4373036524
9  libc++abi.dylib                0x1aa49b0e0 std::__terminate(void (*)()) + 20
10 libc++abi.dylib                0x1aa49deb0 __cxa_get_exception_ptr + 34
11 libc++abi.dylib                0x1aa49de5c __cxxabiv1::exception_cleanup_func(_Unwind_Reason_Code, _Unwind_Exception*) + 138
12 libobjc.A.dylib                0x1aa395d7c _objc_exception_destructor(void*) + 358
13 CoreFoundation                 0x1952724a4 -[NSCache init] + 110
14 UIKitCore                      0x198274a5c -[UIView(Internal) _setViewDelegate:] + 160
15 UIKitCore                      0x19761327c +[UIViewController setViewController:forView:] + 52
16 UIKitCore                      0x19760b5ec -[UIViewController setView:] + 468
17 UIKitCore                      0x19760ac7c -[UIViewController loadViewIfRequired] + 200
18 UIKitCore                      0x19760b334 -[UIViewController view] + 32
19 GoogleInteractiveMediaAds      0x105558204 -[IMAAdViewController viewDidLoad] + 512
20 UIKitCore                      0x197606744 -[UIViewController _sendViewDidLoadWithAppearanceProxyObjectTaggingEnabled] + 108
21 UIKitCore                      0x19760af70 -[UIViewController loadViewIfRequired] + 956
22 UIKitCore                      0x19760b334 -[UIViewController view] + 32
23 GoogleInteractiveMediaAds      0x10554c4d4 -[IMAAdDisplayContainer setAdViewController:] + 336
24 GoogleInteractiveMediaAds      0x105542f00 -[IMAStreamManager handleMessageAdBreakStarted:] + 180
25 CoreFoundation                 0x1952d69a0 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 28
26 CoreFoundation                 0x1952d6948 ___CFXRegistrationPost_block_invoke + 52
27 CoreFoundation                 0x1952d5eb0 _CFXRegistrationPost + 440
28 CoreFoundation                 0x1952d5870 _CFXNotificationPost + 716
29 Foundation                     0x19659c4bc -[NSNotificationCenter postNotificationName:object:userInfo:] + 64
30 GoogleInteractiveMediaAds      0x10555eab0 -[IMAJavaScriptSession didReceiveMessage:] + 324
31 GoogleInteractiveMediaAds      0x10555deb4 -[IMABaseDispatcher processNewMessage:] + 260
32 GoogleInteractiveMediaAds      0x10555dd9c -[IMABaseDispatcher processNewMessageWithChannelName:data:] + 104
33 GoogleInteractiveMediaAds      0x10555d698 -[IMAWebViewDispatcher processNewMessageWithChannelName:data:] + 100
34 GoogleInteractiveMediaAds      0x1055386c0 -[IMAJavaScriptIosBridge webView:didReceiveMessage:] + 168
35 GoogleInteractiveMediaAds      0x10555ce14 -[IMAWKWebView userContentController:didReceiveScriptMessage:] + 180
36 WebKit                         0x1a1b69948 <redacted> + 232
37 WebKit                         0x1a1d742f4 <redacted> + 584
38 WebKit                         0x1a1faf188 <redacted> + 3184
39 WebKit                         0x1a1958a1c <redacted> + 124
40 WebKit                         0x1a1c8d5dc <redacted> + 40
41 WebKit                         0x1a193bc4c <redacted> + 852
42 WebKit                         0x1a193b538 <redacted> + 628
43 JavaScriptCore                 0x19f6645e0 <redacted> + 484
44 JavaScriptCore                 0x19f6652c8 <redacted> + 36
45 CoreFoundation                 0x1952f576c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
46 CoreFoundation                 0x1952f5668 __CFRunLoopDoSource0 + 208
47 CoreFoundation                 0x1952f4960 __CFRunLoopDoSources0 + 268
48 CoreFoundation                 0x1952eea8c __CFRunLoopRun + 824
49 CoreFoundation                 0x1952ee21c CFRunLoopRunSpecific + 600
50 GraphicsServices               0x1acebb784 GSEventRunModal + 164
51 UIKitCore                      0x197d2eee8 -[UIApplication _run] + 1072
52 UIKitCore                      0x197d3475c UIApplicationMain + 168
53 UnivisionNowSwift              0x104772eb4 main + 4370230964 (<compiler-generated>:4370230964)
54 libdyld.dylib                  0x194fae6b0 start + 4
On Tuesday, March 23, 2021 at 1:59:25 PM UTC+8 wave20...@gmail.com wrote:

Hi   Team


  Thanks for your help. we will update the framework 3.14.1 for the next version of App. it will take few days.

adTagUrl :


AssetKey: 

complete stack trace :
Fatal Exception: UIViewControllerHierarchyInconsistency
0  CoreFoundation                 0x19d46586c __exceptionPreprocess
1  libobjc.A.dylib                0x1b2480c50 objc_exception_throw
2  CoreFoundation                 0x19d35e4a4 -[NSCache init]
3  UIKitCore                      0x1a0360a5c -[UIView(Internal) _setViewDelegate:]
4  UIKitCore                      0x19f6ff27c +[UIViewController setViewController:forView:]
5  UIKitCore                      0x19f6f75ec -[UIViewController setView:]
6  UIKitCore                      0x19f6f6c7c -[UIViewController loadViewIfRequired]
7  UIKitCore                      0x19f6f7334 -[UIViewController view]
8  GoogleInteractiveMediaAds      0x102ffc204 (Missing)
9  UIKitCore                      0x19f6f2744 -[UIViewController _sendViewDidLoadWithAppearanceProxyObjectTaggingEnabled]
10 UIKitCore                      0x19f6f6f70 -[UIViewController loadViewIfRequired]
11 UIKitCore                      0x19f6f7334 -[UIViewController view]
12 GoogleInteractiveMediaAds      0x102ff04d4 (Missing)
13 GoogleInteractiveMediaAds      0x102fe6f00 (Missing)
14 CoreFoundation                 0x19d3c29a0 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__
15 CoreFoundation                 0x19d3c2948 ___CFXRegistrationPost_block_invoke
16 CoreFoundation                 0x19d3c1eb0 _CFXRegistrationPost
17 CoreFoundation                 0x19d3c1870 _CFXNotificationPost
18 Foundation                     0x19e6884bc -[NSNotificationCenter postNotificationName:object:userInfo:]
19 GoogleInteractiveMediaAds      0x103002ab0 (Missing)
20 GoogleInteractiveMediaAds      0x103001eb4 (Missing)
21 GoogleInteractiveMediaAds      0x103001d9c (Missing)
22 GoogleInteractiveMediaAds      0x103001698 (Missing)
23 GoogleInteractiveMediaAds      0x102fdc6c0 (Missing)
24 GoogleInteractiveMediaAds      0x103000e14 (Missing)
25 WebKit                         0x1a9c55948 ScriptMessageHandlerDelegate::didPostMessage(WebKit::WebPageProxy&, WebKit::FrameInfoData&&, API::ContentWorld&, WebCore::SerializedScriptValue&)
26 WebKit                         0x1a9e602f4 WebKit::WebUserContentControllerProxy::didPostMessage(WTF::ObjectIdentifier<WebKit::WebPageProxyIdentifierType>, WebKit::FrameInfoData&&, unsigned long long, IPC::DataReference const&, WTF::CompletionHandler<void (IPC::DataReference const&, WTF::String const&)>&&)
27 WebKit                         0x1aa09b188 WebKit::WebUserContentControllerProxy::didReceiveMessage(IPC::Connection&, IPC::Decoder&)
28 WebKit                         0x1a9a44a1c IPC::MessageReceiverMap::dispatchMessage(IPC::Connection&, IPC::Decoder&)
29 WebKit                         0x1a9d795dc WebKit::WebProcessProxy::didReceiveMessage(IPC::Connection&, IPC::Decoder&)
30 WebKit                         0x1a9a27c4c IPC::Connection::dispatchMessage(std::__1::unique_ptr<IPC::Decoder, std::__1::default_delete<IPC::Decoder> >)
31 WebKit                         0x1a9a27490 IPC::Connection::dispatchIncomingMessages()
32 JavaScriptCore                 0x1a77505e0 WTF::RunLoop::performWork()
33 JavaScriptCore                 0x1a77512c8 WTF::RunLoop::performWork(void*)
34 CoreFoundation                 0x19d3e176c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
35 CoreFoundation                 0x19d3e1668 __CFRunLoopDoSource0
36 CoreFoundation                 0x19d3e0960 __CFRunLoopDoSources0
37 CoreFoundation                 0x19d3daa8c __CFRunLoopRun
38 CoreFoundation                 0x19d3da21c CFRunLoopRunSpecific
39 GraphicsServices               0x1b4fa6784 GSEventRunModal
40 UIKitCore                      0x19fe1aee8 -[UIApplication _run]
41 UIKitCore                      0x19fe2075c UIApplicationMain
42 UnivisionNowSwift_TVE          0x102785de8 main (<compiler-generated>)
43 libdyld.dylib                  0x19d09a6b0 start

Thanks,

Let me bring this up with my team. We will get back to you as soon as possible.

Regards,

Aryeh Baker IMA SDK Team

ref:_00D1U1174p._5004Q2DuDR7:ref

[IMA SDK]

Hi Eric,

My team got back to me that given that the you are using both client side and DAI IMA in the same app, one issue may be that the different instances of IMA may not be being properly reused or de-allocated, so I would suggest that you look into whether you can recreate the issue by switching between DAI and IMA content, in as many edge case situations as possible. Without a sample project with reliable replication steps we won't be able to solve this.

[IMA SDK]

Hi there,

I hope you're doing well.

I just want to circle back on this. Could you please confirm if you still encounter the reported issue here?

Regards,

Teejay Wennie Pimentel IMA SDK Team

ref:_00D1U1174p._5004Q2DuDR7:ref

[wave20...@gmail.com]

Hi Team，

  This issue still happens. By the way, we have the same problem with our other project which IMA SDK version is 3.14.1 and it only uses DAI IMA to get the live and Vod stream and Ad. The following is the crash report.

A view can only be associated with at most one view controller at a time! View <IMAWKWebView: 0x11067dd90; frame = (0 0; 414 253); opaque = NO; autoresize = W+H; layer = <CALayer: 0x28173d780>> is associated with <IMAWebUIViewController: 0x115c47c80>. Clear this association before associating this view with <IMAWebUIViewController: 0x118339880>.

Thanks，

Haibo

[IMA SDK]

Hi there,

 

Thank you for writing back.

 

Our team have an ongoing investigation regarding this matter but we are kind of stuck as we can't narrow down the situation that leads to this behavior. Have you been able to reproduce this? Could you please share with us the steps to reproduce the issue and your sample project file implementation where this issue is reproducible? This would greatly help us progress in our investigation. You can send it in our testing alias at imate...@gmail.com.

Regards,

Michael Angelo Legaspi IMA SDK Team

ref:_00D1U1174p._5004Q2DuDR7:ref

[wave20...@gmail.com]

Hi  Team,

       We also can't reproduce this issue. we only can see it in the crash report. 

       the users seem to enter the background when the Ad happens. after few mins they enter the foreground. then the crash happens.

Hope that will help.

Thanks,

Haibo

[IMA SDK]

Hi there,

 

Thank you for providing additional information. Let me see if this can shed a light for current investigation. I will share this to our team and we will get back to you once we have our findings.

Regards,

[wave20...@gmail.com]

     Hi Team,

     

     Do you have any update about this issue?  or do you need us to do something else?

     The following are recently our crash reports.

     

Thanks,

Haibo

[IMA SDK]

Hi,

I'm afraid our team haven't given their feedback yet on the investigation. Once they do, we will make sure for you to be notified.

[IMA SDK]

Hi Haibo,

 

I hope you are doing fine.

 

Our team circled back on this and wants to know if you are still encountering this issue? There seems to be some adjustments and modifications done that is now reflected on the latest version 3.14.4. Would it be possible for you to update to the latest version and see if this would still occur?

Regards,

[wave20...@gmail.com]

Hi Micheal 

  Thanks for writing back. 

  We are still encountering this problem in two of our projects.  We will upgrade these projects and see if it works well.

Thanks,

Haibo

[wave20...@gmail.com]

  Hi Micheal 

    Recently we updated our Apps and the crash issues are still there(the version of Media Ads SDK is 3.14.4). Please help us take a look at it.

Fatal Exception: UIViewControllerHierarchyInconsistency

A view can only be associated with at most one view controller at a time! View <IMAWKWebView: 0x102771f00; frame = (0 0; 0 0); opaque = NO; autoresize = W+H; layer = <CALayer: 0x283b5ca60>> is associated with <IMAWebUIViewController: 0x1027cf190>. Clear this association before associating this view with <IMAWebUIViewController: 0x102789a50>.

Thanks,

Haibo 

[IMA SDK]

Hello Haibo,

 

Thank you for responding back to us.

 

Would you be able to share the sample project implementation where we can reproduce the issue? Or if you have replicated it with our sample apps, point us out directly to what sample app you have used and we will check on our end.

Regards,
 

[wave20...@gmail.com]

Hi  Micheal

   Thank you for your response.

    We can't reproduce this issue. I think it is really hard to reproduce it. We only see it in our firebase crash report.  it happens in our different projects which are built by different teams ( projects are totally different. including encapsulation of IMA SDK is different ). But we got the same crash error.

Thanks,

Haibo 

[IMA SDK]

Hello Haibo,

 

Thank you for reaching out to us.

 

I understand if you can't consistently replicate the issue. However, would you be able to share with us the sample project implementation where the issue occurs? We request this as we need something to test and reproduce on our end and see the exact issue to have better understanding what is causing it.

 

You may send the requested information privately via "Reply To Author" button.

Regards,

[wave20...@gmail.com]

Hi  Micheal

   Thank you for your help.

    Recently we can't provide the sample for this issue. But we found the same issue. please take a look at the following web site. 

    https://groups.google.com/g/ima-sdk/c/gdS51gJv0Q4 

Thanks,

Haibo

[IMA SDK]

Hello Haibo,

 

Thank you for responding back to us.

 

The forum thread you shared is already closed as the user on that thread didn't respond and re-confirm the issue. On your case, since the error seems to be resolved in previous version of the SDK (v3.14.4) and there is no reliable steps to replicate the issue you are reporting now nor a sample project implementation we can use to reproduce it and investigate, I'm afraid that we are left with nothing to continue investigating the case. Should you found a way of reproducing the same behavior in one of our sample apps or with your own project, do not hesitate to come back to us with more information.

Regards,

[wave20...@gmail.com]

Hi  Micheal 

   Thank you for your response.

   I  just made a test that is the same steps as (https://groups.google.com/g/ima-sdk/c/gdS51gJv0Q4) using IMA SDK (v3.14.5). I still can reproduce the crash issue.

   "I started the app and then played the video. I would then start instruments to monitor memory allocations. Eventually, the app would crash with this error."

   

    The following are the sample for testing and the crash report.

     https://www.dropbox.com/s/41ntbz3q62joqpo/googleads_ima_ios_dai_objc_advanced_example%202.zip?dl=0

*** Terminating app due to uncaught exception 'UIViewControllerHierarchyInconsistency', reason: 'A view can only be associated with at most one view controller at a time! View <IMAWKWebView: 0x7fa162f34f10; frame = (0 0; 428 306.333); opaque = NO; autoresize = W+H; layer = <CALayer: 0x600001e19a40>> is associated with <IMAWebUIViewController: 0x7fa1648acb80>. Clear this association before associating this view with <IMAWebUIViewController: 0x7fa162eae320>.'

terminating with uncaught exception of type NSException

CoreSimulator 776.3 - Device: iPhone 12 Pro Max (B2F37766-2E94-4CAD-B958-D76648FE1157) - Runtime: iOS 14.4 (18D46) - DeviceType: iPhone 12 Pro Max

Thanks,

Haibo

[IMA SDK]

Hello Haibo,

 

Thank you for responding back to us.

 

This seems to be an edge case as there are no other known steps to reproduce this issue in our sample apps or even on your own project implementation, other than how it was describe in this related case (https://groups.google.com/g/ima-sdk/c/gdS51gJv0Q4). Nonetheless, I have relayed this to the rest of our team for further investigation to see if we can find anything that could possibly point out the cause of the issue and resolution if possible. For the meantime, you can share with us anything that comes up on your end that will help resolve the issue, like screen recording of your own testing or any other relevant information. We will update you the soonest we have sufficient information on our end.

Regards,

[IMA SDK]

Hi everyone,

I have heard from myteam that upgrading to the latest IMA SDK version has resolved the issue. Please get back to us if on the newest SDK version this still occurs.

Regards,

Aryeh IMA SDK Team

ref:_00D1U1174p._5004Q2DuDR7:ref