![]() ![]() If it did, I imagine being able to collect information whenever the app makes a successful request that would have failed if ATS were enabled. As far as I can tell, ATS doesn't have any kind of "warn-only" mode that could be used for this sort of purpose. What I'd like to be able to do, is identify how many and which users might be affected if ATS were enabled. I'd like to enable ATS, but there is some fear that doing so could break connectivity for some of our users. I have an app that's been around a long time, and it disables ATS (with NSAllowsArbitraryLoads set). Invalid batch updates detected: the number of sections and/or items returned by the data source before and/or after performing the batch updates are inconsistent with the updates.ĭata source before updates = This issue occurs in iOS 16.4.1 and MacOS 13.3.1 (Apple Silicon). But this has changed in a recent iOS update. This used to be no problem as the CollectionView is lower on the navigation stack and not displayed at the time the alteration occurs. From there it is possible to delete the item which removes it from the data source of the CollectionViewController and leads to the crash. When a CollectionView item is tapped the UIImageView will be pushed on top of the navigation stack to display this item. However the change is made when the UICollectionView is not displayed which used to be allowed but now causes a crash. The crashes are due to the data source being changed without properly updating the ViewController. Since a recent iOS update somewhere between 16.2 and 16.4.1 a change was introduced that now leads to UICollectionViewController crashing in my app. Thread 4 name: Dispatch queue: Ġ libsystem_kernel.dylib 0x20a827674 _pthread_kill + 8ġ libsystem_pthread.dylib 0x21af8b1ac pthread_kill + 268Ģ libsystem_c.dylib 0x1d4388c8c abort + 180ģ libc++abi.dylib 0x21aecab8c abort_message + 132Ĥ libc++abi.dylib 0x21aebaa80 demangling_terminate_handler() + 336ĥ libobjc.A.dylib 0x1c5ea1d3c _objc_terminate() + 144Ħ libc++abi.dylib 0x21aec9f28 std::_terminate(void (*)()) + 20ħ libc++abi.dylib 0x21aec9ec4 std::terminate() + 56Ĩ libdispatch.dylib 0x1d4324f9c _dispatch_client_callout + 40ĩ libdispatch.dylib 0x1d432c640 _dispatch_lane_serial_drain + 672ġ0 libdispatch.dylib 0x1d432d18c _dispatch_lane_invoke + 384ġ1 libdispatch.dylib 0x1d4337e10 _dispatch_workloop_worker_thread + 652ġ2 libsystem_pthread.dylib 0x21af84df8 _pthread_wqthread + 288ġ3 libsystem_pthread.dylib 0x21af84b98 start_wqthread + 8 The app is built by EAS CLI (version 3.10.0) (Expo Application Services) ![]() ![]() The app is developed by React Native (version 0.70.5), using the Expo framework (Expo SDK 47) Tests on AWS Device Farm with iPhone 13 (iOS 16.0.2) and iPhone 13 Pro (iOS 15.2) (the only iOS versions supported) passed, suggesting that it's not a device-specific issue. This indicates that the issue may be happening before Sentry launches.ĭevices crashing are iPhone 13 (iOS 16.3, iOS 16.4) and iPhone 13 Pro (iOS 16.2). Sentry has been installed to catch errors but didn't detect any error when the app crashed on launch. One user experiencing the issue was on the same WiFi network as another user without the issue, suggesting that it was not a network-related problem. Issue reported in Singapore and Thailand, but not specific to the region as some other apps in those countries work well. Some details that may help in identifying the issueĪpp crashes on launch on some devices, but most devices work without issues. If you have any insights or suggestions on how we can proceed, please let us know, thanks! ![]() We've tried many things but still can't figure out the problem and also can't reproduce it. However, it crashes on launch on some devices, while most of the other devices work fine. My app has been approved by Apple and is available on the App Store. ![]()
0 Comments
Leave a Reply. |