-
-
Notifications
You must be signed in to change notification settings - Fork 448
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
Android Global Crash Reporting (using Email) #335
Comments
@ISNIT0 Sorry for the delay in my answer. This looks promising. The problem is that you need a way to send the feedabck per email in a secure way (no open SMTP server, no password hardcoded in app). Have you plan? Does Google do not provide an integrated way to gather this kind of "customized feedback"? |
@kelson42 afaik you can achieve that using Google Firebase, but on the other side it wouldn't work if the user has no Google Apps installed, which tends to happen often nowadays. |
@divadsn interesting. I'm not so concern about that as 99% of our user download the app through the Play store. I'm more concern about other privacy violoation that might imply the usage of Google Firebase. |
The suggestion here is that it uses people's personal email provider (opens their email app), so everything is transparent etc. No hidden analytics/email sending from us |
And we could create a google group type email address which receives all the messages |
@kelson42 I think you can set up a "magic email link" that will autopopulate the data and will open in the users email app that they can then send. |
This code just uses Android intents |
|
Yes please - do you think it should be "feedback"@ ? |
maybe a bit more specific like android-crash-feedback@ ? |
I was thinking it'd be good to keep it friendly and easy for anyone to submit private feedback anyway? |
@ISNIT0 yes, but we have already contact@kiwix.org and I do not want to mix this kind of "special reports" with more traditional ones. |
Okay - sure, android-crash-feedback then :)
|
Email box created and credentials communicated to @ISNIT0 @julianharty @mhutti1 |
@ISNIT0 It seems the code has been merged for this!? Can we close that ticket? |
@kelson42 I don't think it has been merged yet. Still some build issues - I'll look into it this week, then we can close all 3 of these issues 👍 |
Considering that nobody works on this and seems to really want to push this I propose to abandon that task. |
This was actually merged a while ago, clearly I forgot to close this issue 🤷♂ |
Well if that is the case then I will close this issue |
Context:
At the recent UK hackathon, the branch
ISNIT0/crash-handler
was created. This implements a new Activity which is opened instead of a fatal app crash. It asks the user what information they would like to supply the developers (if any) and then opens an email client (using an Android intent) with pre-filled information.The current implementation looks as follows:
This thread is about the mode of transport we use - email
Pros to using email:
Cons to using email:
My personal view is that we should go ahead with email, but consider changing it going forward.
Source Email Thread:
The text was updated successfully, but these errors were encountered: