I am using Google-Mobile-Ads-SDK 7.56.0.The user with the error is using iOS 10 on iPhone 5.
Error slack trace:
Hi Hyunjoon,
Thank you for reaching out to us.
Upon investigation of the crash log that you've provided, it seems that the fatal exception is stemming from a common iOS function (NSConcreteFileHandle writeData) rather than an AdMob SDK one. With this in mind, I would recommend reaching out to more iOS-centric support sites (such as StackOverflow) for further assistance on this one, as I'm afraid that we can only assist you on technical AdMob-specific concerns.
Regards,
Ziv Yves Sanchez
Mobile Ads SDK Team
Hi Hyunjoon,
Thank you for providing additional context on your concern.
It is true that the NSConcreteFileHandle may have been called by the AdMob SDK during its operation. Could you try freeing up space on your device, and checking if the issue still happens afterwards? If the issue does still persist despite the above, you may then kindly provide the details below (via Reply privately to author) so that I can further investigate the issue:
Last Exception Backtrace : 0 CoreFoundation 0x000000018ad285f0 ___exceptionPreprocess + 224 1 libobjc.A.dylib 0x000000018aa4abcc objc_exception_throw + 44 2 Foundation 0x000000018b0b33a0 -[NSConcreteFileHandle readDataUpToLength:error:] 3 Foundation 0x000000018b042fc0 -[NSConcreteFileHandle writeData:] + 284 4 QQKSong 0x000000010249fb38 _GADResourceBufferCanProvideByteOffset + 6884 5 libdispatch.dylib 0x000000018a9ee524 __dispatch_client_callout + 16 6 libdispatch.dylib 0x000000018a9a10b0 __dispatch_lane_barrier_sync_invoke_and_complete + 56 7 QQKSong 0x000000010249f96c _GADResourceBufferCanProvideByteOffset + 6424 8 CFNetwork 0x000000018e11b01c _CFNetworkHTTPConnectionCacheSetLimit + 204964 9 Foundation 0x000000018b0eefa0 ___NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 16 + 16 10 Foundation 0x000000018affa2c0 -[NSBlockOperation main] + 84 11 Foundation 0x000000018b0f11fc ___NSOPERATION_IS_INVOKING_MAIN__ + 20 12 Foundation 0x000000018aff9fc4 -[NSOperation start] + 740 13 Foundation 0x000000018b0f1bf4 ___NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION__ + 20 14 Foundation 0x000000018b0f16c0 ___NSOQSchedule_f + 180 15 libdispatch.dylib 0x000000018a9a0c8c __dispatch_block_async_invoke2 + 104 5 libdispatch.dylib 0x000000018a9ee524 __dispatch_client_callout + 16 17 libdispatch.dylib 0x000000018a996e98 __dispatch_continuation_pop$VARIANT$mp + 412 18 libdispatch.dylib 0x000000018a9965ec __dispatch_async_redirect_invoke + 656 19 libdispatch.dylib 0x000000018a9a3438 __dispatch_root_queue_drain + 376 20 libdispatch.dylib 0x000000018a9a3bf8 __dispatch_worker_thread2 + 124 21 libsystem_pthread.dylib 0x000000018aa3fb38 _pthread_wqthread + 204 22 libsystem_pthread.dylib 0x000000018aa42740 start_wqthread + 8 Exception Type: NSFileHandleOperationException(SIGABRT) Exception Codes: *** -[NSConcreteFileHandle writeData:]: No space left on device at 0x000000018ab1dd88 Crashed Thread: 21
Hi there,
Thank you for reaching out to us and for providing the details.
Allow me to raise this with the rest of the team to further investigate the issue. I'll get back to this thread once an update is available.
Regards,
Mark Albios
Hi there,
Thanks for getting back to us.
Currently, there is still no update for this; however, allow me to make a follow up with the team. We'll be updating this thread for any available feedback.
Regards,
Mark Albios
Mobile Ads SDK Team
Hello Everyone,
This is to provide an update to the issue as discussed on this thread.
"As the error states, this looks like it is due to the SDK trying to write out data with a full disk. A try/catch to prevent this was added to 8.6.0, so the publisher is encouraged to update to the latest SDK."
Regards,
|
||||||