You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when and Advertisement is shown for a website (Not another App, when taken to Google Play Store, App allows you to come back to Kitchensink App) the ClickURL takes user to the Website within a browser in the WL KitchenSink app. Hitting Back hardkey does not take user back to Kitchensink app. User is stuck on ClickURL's webpage until force close
Actual:
Unable to return from ClickURL Advertisement Webpage
Expected:
ClickURL Webpage to be displayed either in an external browser window (not within the kitchensink app), or user is able to return from webpage by hitting the Back button.
Repro:
Launch WL Kitchensink Sample App v3.07
Open Advertisement Page
Call for Ad
Wait until an Advertisement for another webpage is displayed
Click on Ad
Try hitting back or returning to KitchenSink app
Notice User is now "stuck" in the ClickURL webpage until force closing the app
The text was updated successfully, but these errors were encountered:
tarasklimenko
changed the title
Ads - After hitting Adding, taken to ClickURL, can't return to the app without force close
Ads - After hitting Ad, taken to ClickURL, can't return to the app without force close
Jul 25, 2014
Description:
Currently when and Advertisement is shown for a website (Not another App, when taken to Google Play Store, App allows you to come back to Kitchensink App) the ClickURL takes user to the Website within a browser in the WL KitchenSink app. Hitting Back hardkey does not take user back to Kitchensink app. User is stuck on ClickURL's webpage until force close
Actual:
Unable to return from ClickURL Advertisement Webpage
Expected:
ClickURL Webpage to be displayed either in an external browser window (not within the kitchensink app), or user is able to return from webpage by hitting the Back button.
Repro:
The text was updated successfully, but these errors were encountered: