GoogleChrome / GoogleChrome/android-browser-helper

TWA toast error

Open
#410 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
832
Forks
370
Avg merge
1d 3h
Merged PRs (30d)
6

Description

Hello,

We're currently using AppAuth library and defining a CustomTabsIntent with the property : TrustedWebUtils.EXTRA_LAUNCH_AS_TRUSTED_WEB_ACTIVITY

It allows us to use TWA. It works pretty well (same app / endpoint for all the tests) but sometimes, we have an error with the TWA. We have no idea why, sometimes a Toast appears saying " Digital asset links verification failed on $MY_URL".

First: why sometimes do we have an error ? We are always using the same app / endpoint, so same fingerprint, same place for the digital asset links...

Second: is there anyway to remove this toast ? Because it will display the custom tab intent with the bar etc.. but this toast is really annoying and provides a really poor UX.

Thank you,

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the TWA launch using AppAuth's CustomTabsIntent and TrustedWebUtils.EXTRA_LAUNCH_AS_TRUSTED_WEB_ACTIVITY, then investigate the intermittent digital asset links verification failure for the reported URL. Done means identifying why verification sometimes fails and determining whether the toast can be removed without preventing the custom tab fallback.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.