Assigned
Status Update
No update yet.
Comments
mj...@gmail.com
Can you provide the below requested information to better understand the issue:
Device used
Which device did you use to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Device used
Which device did you use to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
ra...@google.com
I cannot reproduce the issue on my side with a sample app. I have this in production.
Conditions to have this crash:
- Android 8.0.0, whatever the manufacturer (Samsung, Sony, LG…)
- Have the Accessbility Service enable (which is for an optional feature on my application)
Into the last 7 days I got few thousands of users affected which represents 5% of users with both conditions.
I understand this bug is now fixed on your side (because I don't have any report on 8.1 for example) but as Android 8.0 is more and more deployed I have more crash reports everyday.
It can be really very useful to have a workaround from our application side to avoid this issue rather than just "wait for 8.1 to be more deployed".
Conditions to have this crash:
- Android 8.0.0, whatever the manufacturer (Samsung, Sony, LG…)
- Have the Accessbility Service enable (which is for an optional feature on my application)
Into the last 7 days I got few thousands of users affected which represents 5% of users with both conditions.
I understand this bug is now fixed on your side (because I don't have any report on 8.1 for example) but as Android 8.0 is more and more deployed I have more crash reports everyday.
It can be really very useful to have a workaround from our application side to avoid this issue rather than just "wait for 8.1 to be more deployed".
mj...@gmail.com
Are you able to reproduce this on Pixel or Nexus devices? If so could you please take a video and share the complete bugreport with us ?
is...@google.com
wi...@gmail.com
I cannot reproduce it on my side.
In copy one crash report I got from Crashlytics on a Nexus 6P yesterday.
In copy one crash report I got from Crashlytics on a Nexus 6P yesterday.
kh...@gmail.com
Since this issue does not happen on latest O (8.1) build on Nexus (as per
mi...@gmail.com
I understand… even if we are all aware that it's not going to happen, they won't do anything.
Alright, I will just wait a couple years for them to update their users.
Alright, I will just wait a couple years for them to update their users.
Description
mailto: links behave different in AMP vs HTML within Gmail web. HTML version will open a compose window within Gmail. AMP mailto: links open at the system level (in Win10) and if set to open in browser, will open in a blank new window.
If appropriate, a small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup, without external dependencies.
Behavior is triggered by even simple mailto: links, including <a href="mailto:test@example.com">email</a>
What steps will reproduce the problem?
1. Include simple <a> tag with href="mailto:..." value
2. Send with HTML and AMP versions
3. HTML will work as expected, AMP does not
What is the expected output? What do you see instead? If you see error messages, please provide them.
Expected output is opening gmail compose window. Observed output is a blank new window or system dialog depending on system settings for handing mailto:
Please provide any additional information below.