Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Enable Share button for profiles that never finish symbolication
See original GitHub issueThe UI blocks sharing profiles that are not symbolicated as users clicked share too early. We have reports of failed symbolication (Bug 1414383 and maybe other unknown reasons) for which users can never share profiles for investigations.
Ideas:
Cancelbutton in “Symbolicating …” overlay. Might appear after 10s to prevent accidental clicking.- Enable
Sharebutton after 15s symbolication. - Double-confirmation prompt when Share (… will users read this?)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:16 (16 by maintainers)
Top Results From Across the Web
How To Enable Facebook Share Button - YouTube
In this video, I walk you through the steps you can take to enable and disable the share button. Keep in mind that...
Read more >Share extension - App not showing … | Apple Developer Forums
Our share extension does not show up in the share sheet the first time you tap the share button. But if you dismiss...
Read more >How to symbolicate crash log Xcode? - Stack Overflow
Click on the View Devices Logs button. Drag-and-drop the crash file to the left panel. The file must end with a .crash extension,...
Read more >Crash Symbolication - Countly
Crash Symbolication lets you symbolicate/de-obfuscate crash reports and convert them into human readable format, helping you pinpoint...
Read more >Sharing a file - Android Developers
Once you have set up your app to share files using content URIs, you can respond to other apps' requests for those files....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I don’t see a problem with having it always available, that way it behaves more deterministically for the user, and is probably a simpler implementation.
I think my preference would be to have the following behavior: