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

fix: Location services availability crash #WPB-11304 #3564

Merged
merged 2 commits into from
Oct 30, 2024

Conversation

m-zagorski
Copy link
Contributor

@m-zagorski m-zagorski commented Oct 29, 2024

BugWPB-11304 [Android] C apps on ss4sk device crashing when sharing location

https://wearezeta.atlassian.net/browse/WPB-11304

What's new in this PR?

Issues

When location services were removed from device - checking for their availability is crashing the application

Solutions

We need to try/catch the error.


PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

Copy link
Contributor

github-actions bot commented Oct 29, 2024

Test Results

863 tests   863 ✅  12m 4s ⏱️
119 suites    0 💤
119 files      0 ❌

Results for commit 6057208.

♻️ This comment has been updated with latest results.

Copy link

Copy link
Contributor

APKs built during tests are available here. Scroll down to Artifacts!

message = "Checking for location services availability failed",
throwable = e
)
false
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

returning false here will make it seems like location is only disabled when the whole API is missing, maybe returning an Either or an Enum to reflect the state is better for usability, what do you think @m-zagorski

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we were to display different message for the end users it would make sense to have some kind of enum or something else here, but as long as we're about to rely on what we have currently (ie the message about location not available) it probably doesnt make sense.

@m-zagorski m-zagorski merged commit fccf8c8 into release/cycle-4.6 Oct 30, 2024
13 of 14 checks passed
@m-zagorski m-zagorski deleted the fix/location-service-availability-crash branch October 30, 2024 14:29
@echoes-hq echoes-hq bot added the echoes: unplanned Any work item that isn’t part of the product or technical roadmap. label Nov 5, 2024
@yamilmedina yamilmedina changed the title fix: Location services availability crash #WPB-11304 fix: Location services availability crash #WPB-11304 Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
echoes: unplanned Any work item that isn’t part of the product or technical roadmap. size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants