Skip to content
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

Crashing in connectionStatus() on app start #290

Closed
tristan-warner-smith opened this issue Jan 25, 2024 · 0 comments · Fixed by #295
Closed

Crashing in connectionStatus() on app start #290

tristan-warner-smith opened this issue Jan 25, 2024 · 0 comments · Fixed by #295
Assignees
Labels

Comments

@tristan-warner-smith
Copy link

Describe the bug
On app start we're getting crashes pointing to the segment library.
The Xcode crash logger seems to show two parallel calls in different threads to AppleUtils.connectionStatus() referencing an unsafe pointer.

To Reproduce
Steps to reproduce the behavior:

  1. Start app
  2. Dispatch analytics events
  3. See error

Expected behavior
No crashes

Screenshots
If applicable, add screenshots to help explain your problem.
The two concurrent calls:
Screenshot 2024-01-25 at 09 52 25
Screenshot 2024-01-25 at 09 53 39

Stack traces of other Segment threads:
Screenshot 2024-01-25 at 09 48 22

Screenshot 2024-01-25 at 09 44 03 Screenshot 2024-01-25 at 09 49 02

Platform (please complete the following information):

  • Library Version in use: 1.4.8
  • Platform being tested: iOS
  • Integrations in use: Firebase, TwilioEngage

Additional context
Add any other context about the problem here.

@tristan-warner-smith tristan-warner-smith changed the title Crashin in connectionStatus() on app start Crashing in connectionStatus() on app start Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants