@Raviraj Thank you for the response.
We’re currently in the process of upgrading our app to align with the latest platform version (v2.3/v3.0), and would like to clarify a couple of additional points to ensure a smooth and controlled transition for our users:
1. Manual Update Preferred Over Auto-Update
We would prefer not to auto-update the app for existing users. Our intent is to ensure users consciously opt-in to the updated version by manually clicking the “Update” button. This is to avoid any unforeseen disruptions and give our users full control over when they transition to the latest version.
Could you please confirm the required configurations or metadata changes we need to make in our app submission to disable auto-update and enforce manual updates for all users?
2. Intermittent API Errors During Local Testing
While performing local testing of the upgraded app using the FDK, we encountered intermittent 502 Connection Establishment errors while calling certain APIs. Following the community advice shared here: Connection Errors on FDK, we were able to mitigate the issue in our local setup.
However, we are concerned about similar issues arising post-deployment in the production environment, as this could impact our users.
Could you advise on:
- Whether these errors are exclusive to the FDK/local environment?
- Any best practices or guidelines to ensure this doesn’t occur in production after the app is published?
Our goal is to ensure that the upgrade is smooth, stable, and non-disruptive for existing users, while also having a clear rollback path in the unlikely event of any post-deployment issues.
Looking forward to your guidance on these points.
Best regards,
Anant