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: Don't try to load bugsnag by name #623

Merged
merged 1 commit into from
Oct 30, 2020

Conversation

cbrevik
Copy link
Contributor

@cbrevik cbrevik commented Oct 30, 2020

Recursive loading by SoLoader should catch them anyway. And retry-logic
in 0.9.0 might fix the bugsnag problems

Recursive loading by SoLoader should catch them anyway. And retry-logic
in 0.9.0 might fix the bugsnag problems
@cbrevik cbrevik requested a review from mikaelbr October 30, 2020 21:18
@mikaelbr
Copy link
Collaborator

mikaelbr commented Oct 30, 2020

I don't think this will fix the bugsnag issue. As mentioned, bugsnag uses system.utils directly so I don't think upgrading soloader would do anything (unless soloader overrides something, but afaik that's not possible with Java). But if this fixes the crashing I'm fine with reverting the changes.

@cbrevik cbrevik merged commit f6411b9 into master Oct 30, 2020
@cbrevik cbrevik deleted the cbrevik/fix-android-soloader-crash branch October 30, 2020 21:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants