The "Blog" link in the ioPay side menu redirects to a "404 | This page could not be found" error. The link is likely pointing to a deprecated URL or an incorrectly formatted path.
User Friction: Prevents users from accessing official announcements, security updates, and ecosystem news directly from the app.
Brand Trust: Encountering 404 errors within a financial/crypto app can diminish user confidence in the platform’s maintenance and reliability.
Engagement Loss: Significant drop in traffic to IoTeX marketing content and community educational materials.
Launch the ioPay.me.
Open the side navigation menu.
Tap the "Blog" menu item.
Observe the 404 error page in the webview.
Expected: Opens https://iotex.io/blog (or the relevant active blog URL).
Actual: Displays a 404 error screen.
URL Update: Verify the current hardcoded URL in the app’s navigation config. If the blog has moved (e.g., from a subdomain like blog.iotex.io to a path like iotex.io/blog), update the source string.
Server-Side Redirect: If the old URL is still receiving traffic, implement a 301 Permanent Redirect on the web server to point all "old blog" traffic to the new destination.
Remote Config: Move menu URLs to a remote configuration file (like Firebase Remote Config) rather than hardcoding them in the binary. This allows the team to fix broken links instantly without requiring a full app store update.
Fallback Logic: Implement a "Check for Updates" or a default homepage fallback if a 404 status code is detected within the internal browser.
Wallet Address: io1tkw393kejmxwnd454twc6020sxcyvh5dxqmren
Device & Environment:
-Operating system: Android 13
-Device model: Redmi Note 10 Pro
Please authenticate to join the conversation.
In Review
New Issue
About 4 hours ago

cryptotestnet
Get notified by email when there are changes.
In Review
New Issue
About 4 hours ago

cryptotestnet
Get notified by email when there are changes.