-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ExternalAccessory:-[EASession _endStreams] crash on our app. #1893
Comments
@84798012 Is this issue related to bug report #1892? Have you been able to reproduce this while testing? This crash log does not provide much information to reproduce so it would be difficult for us to find the bug or figure out if we fixed the issue. Could you provide some more information to help us with our debugging:
|
|
Pull request #1910 notes it should resolve this issue. |
@84798012, can you please retest using iOS 7.2 and advise if you are still experiencing the issue? Thank you! |
Closing as inactive. Reporter can advise if issue is still present in iOS 7.2, and we can reopen if needed. |
Hi, theesalech. This issue is reported by Apple's crash report from our product, not from myself. I'm sorry that I not sure what happens on our customers. Here I attached is all what I got. And it seems that your team have fixed this issue before, but in new version SDL, this issue not be fixed. |
Hi @84798012 , can you please confirm that you have updated your app to use SDL iOS 7.2.0? If you are still getting the crash report when using SDL iOS 7.2.0, we will need more details in order to work on finding the root cause. Please provide recent crash logs from the crash when using version 7.2.0, and any other details of the issue. You should be able to leave an additional comment on this closed issue with that information. We can then re-open the issue to investigate further. Thank you! |
Sorry theesalech, I can not use SDL 7.2.0 now. Because we have informed this issue been fixed in 7.1.0, and we have upgrade to 7.1.0. It caused more crash reports from apple, so we had to rollback to 7.0.0. I'm afraid that if upgrade to 7.2.0, this issue still not been fix. Our manager can not accept so many crash in our app, so please double confirm if this issue really been fixed. And are you sure you have make new fix in 7.2.0 ? |
Hi @84798012, we cannot reproduce this issue, so our fixes are at best just trying something that we think might fix it. Were the crash reports on v7.1.0 different than the ones from v7.0.0? We must continue to request recent full crash logs, SDL file logs if you can enable them, and any other details (such as information from your own analytics of when this crash occurs). |
Hi @84798012 , we're following up here to see if you're able to provide any additional details of your issues that would help in our investigation. Please advise if you have crash logs, SDL file logs, etc. that can be shared. Thank you! |
Attaching logs as requested. Issue reoccurring once the partner updated to 7.2 |
Hi @cmckee16, Thanks for providing the logs. Can you please share the reproductions steps used to obtain the "Issue 1" logs so our team is able to investigate? After review of the logs it looks like the 2-5 logs may be for different issues and not for issue 1893; if that is not the case please also provide reproduction steps for those issues as well. Thanks! |
Sorry, Jordyn, I can not provide how to reproduce steps. All the crash report are from Apple's crash report. |
Hi @cmckee16 and @84798012, the attached crash report does not have any mention of SmartDeviceLink, and therefore unfortunately does not provide much insight into the issue, making it difficult for Livio to assist in identifying/resolving the problem. The following (in priority order) would be most helpful for continuing the investigation. Thank you!
|
Bug Report
[Summary]
We recieved crash report from apple organizer.
Reproduction Steps
I'm not sure when cause this crash, but received from apple report.
Expected Behavior
No crash.
Observed Behavior
Have crash.
OS & Version Information
The text was updated successfully, but these errors were encountered: