For Apps with In-App Browser:
If you've already implemented an in-app browser within your native mobile app, but your app is still being detected for WebView transactions, here are a few possible reasons:
-
Older Versions of the App:
Some users may still be using older versions of your app that haven't been updated with the new in-app browser functionality. Ensure all users are on the latest version to prevent WebView transactions from being registered. -
Sharing the Singpass Client ID with a Web Application:
If the Singpass Client ID is shared with a web application, WebView transactions can still be detected if users open your web app from within a third-party app (e.g., WeChat or other messaging apps). This can cause the transaction to be registered as a WebView transaction instead of an in-app browser.
For Web Apps (No Native Mobile App):
If your service is primarily a web app and not a native mobile app, there may be other scenarios that lead to WebView transactions:
- Accessing Through Third-Party Apps:
Some users might access your web application through other apps that open web content in a WebView. This can inadvertently trigger WebView transaction detection, even though your web app was not intended to be accessed in a WebView.
What Should You Do?
- For native mobile apps: Ensure all users are on the latest version of your app with the in-app browser properly implemented. If your Singpass Client ID is shared with a web app, consider isolating it to prevent cross-app WebView launches.
- For web apps: No action is required on your part if you do not have a native mobile app.
Comments
0 comments
Please sign in to leave a comment.