Hi, I am using Location Push Service Extension in my app but as soon as my app gets an update Location Extension fails to launch. From the console I can see OS is terminating this process. What could be the reason ? When user launches the app after update the extension starts to work as expected.
Extensions not working after an app update was a known problem a while ago, but has been fixed since iOS 17.5
Are you seeing this issue on a later iOS version?
Hi, Thanks for responding. I am seeing this issue on iOS 18.3.2 also
Can you please file a bug report on this at https://developer.apple.com/bug-reporting
Please also create and attach a system diagnostic log to your bug report, by going to https://developer.apple.com/bug-reporting/profiles-and-logs/ and following the instructions for APNs for iOS to install a logging profile on your device. Then reproduce the issue, and follow the instructions at the above link to create a sysdiagnose. And attach that to the Feedback report as well.
You would want to reproduce the problem, and quickly after the reproduction, create the sysdiagnose. Make sure to include the Bundle ID of your app in the comments.
When completed, please post the Feedback ID here.
Thank you. I will follow these steps and submit the feedback. Once feedback is created I will share the feedback Id.
Created the feedback having Id - FB18350013
@Engineer , I have created the Feedback having Id - FB18350013
Is there a way this can be prioritized ? Thanks
You have not attached a diagnostic log (sysdiagnose) as requested, and instead attached an apk package which does not have any use to us.
We cannot proceed with this Feedback without a sysdiagnose showing the reproduction of the problem.
@Engineer I have attached the diagnostic log (sysdiagnose) in feedback FB18350013. Can you please check now. Thanks
@Engineer , Do you have any further updates for feedback FB18350013? If you need any other details please let me know. Thanks
The current status of your Feedback can be viewed in Feedback Assistant under Resolution. Here you can track if the report is still being investigated, has a potential identified fix, or has been resolved in another way.
For more details on Feedback Status, please see “Understanding Feedback Status” at https://developer.apple.com/bug-reporting/status.
@Engineer , Thank you. I just wanted to get my feedback screened by the Core Location team during Bug Review calls at Apple :)
@Engineer , We have replicated the issue again and this time Location Extension did not even launch. We have attached the sysdiagnose file of this scenario in the feedback. Please let me know if any further details are needed but we are waiting for some updates from Apple dev support.
@connecttorohit What do you mean by "this time Location Extension did not even launch". That was your original issue, when you said "Location Extension fails to launch".
What is different this time?
Also, we will see what we can do with this last sysdiagnose, but it is missing crucial debug information. Please install the logging profile I mentioned above, and keep reinstalling it every few days - as it automatically expires - until you see another repro of the problem, so when you create the sysdiagnose at that point we can see the detailed debug information we need.
Also include the following info in your bug report:
@Engineer , We are seeing 2 symptoms Symptom 1: Location Extension launches but gets killed by OS - This scenario is captured in the sysdiagnose files attached on 06/26
Symptom2: Location Extension does not launch. There is no info about the extension process in Console logs. This scenario is captured on sysdiagnose files attached on 07/10
I will get new logging profile and try to recreate the scenario and capture sysdiagnose again, meanwhile if you can please review the sysdiagnose logs attached on 06/26 and let me know if it provides some info. Thanks
@connecttorohit The last sysdiagnose is hard to figure out because it's missing information, and we also need the other push information I asked for.
I will wait for the new repro with the full sysdiagnose and the detailed push info.
In the meantime someone from the team might be able to look at it and understand the issue, but better with the full info.