Assigned
Status Update
No update yet.
Comments
jp...@google.com
Are you using Linkify?
bl...@google.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)
ri...@gmail.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".
Description
Hi Google Support,
Description
This Venkateswarlu Abburi from Ripple Street engineering team. We would like to adopt Dynamic email content in our platform communications to our end users. As per the guidelines our team has submitted the amp for email registration request on 9th January along with email toampforemail.whitelisting@gmail.com and registration form. Please review and approve the request. Do let us know further steps if any.
Form Address for Whitelisting:no-reply@ripplestreet.com
Developer contact address: dev@ripplestreet.com
Impact
AMP/Dynamic email adoption is kind of paused as of know as we are waiting for approval.
Thanks, Venkateswarlu Abburi, Ripple Street, Engineering Team.