We recently updated our File Viewer Plugin to its latest version.
The new client actions are working in both DEV and UAT environments but are not working in our Production. We can only use the deprecated actions at the moment.
We are using default extensibility settings in all environments.
Hi @Edwin Siruma ,
I think there could be a few different scenarios here. After upgrading to the latest version, did you rebuild the mobile app? As you know, modifying or upgrading a plugin requires generating a new build so the changes are included. Since you mentioned it’s working in DEV and UAT, I assume the rebuild was done.
If that’s the case, have you checked whether the new updates were actually deployed correctly to Production (in case it’s a deployment issue)? You can confirm this by checking the version number or version code in Service Center across the three environments. In DEV and UAT they should match, and if Production shows a different value, it would indicate the app is still running on an older build. This would point more toward a deployment issue, or it could mean Production requires a clean rebuild of the app.
Please check those points and let us know.
Yes app is rebuilt and all environments are now in MABS 11.1
That’s good to know that all environments are already on MABS 11.1. Just to clarify though MABS mainly handles the build process itself, so it doesn’t necessarily guarantee that the latest plugin version is being used.
The next step I’d recommend is checking the actual version number and version code in Service Center across DEV, UAT, and Production. Even if the MABS version is consistent, there can still be a mismatch if the Production build didn’t fully include the updated plugin changes.
If you notice that the Production version is lower or different from DEV/UAT, that would explain why the new client actions aren’t working and only the deprecated ones are available. In that case, performing a clean rebuild specifically for Production should resolve it.
What i am trying to say, Around 80% of the issue is deployment-related especially since DEV and UAT are working as expected. That means focusing on manual checks and configurations in Production is usually the best way to troubleshoot and narrow down the root cause.
Check everything related to deployment.
Version and extensibility are the same across all the environments.
I first saw this error in 3.0.1 version I was hoping 3.0.2 release was the fix, but the situation is the same for both versions.
Thank you for checking.
No problem at all, Edwin.
One last suggestion could you check the logic inside the File Viewer actions directly in Production and compare it with the versions in DEV or UAT? Since those environments are working fine, this comparison might reveal any subtle differences, even if the versions look identical in Service Center.
If you find differences, you can (not recommended, but possible as a quick check) manually recreate the same logic from UAT into the corresponding Production action. Just make sure to copy only the flow logic inside the action rather than the entire action itself to avoid reference or deployment issues.
And don’t worry about overwriting as long as the changes are identical, it won’t cause any harm. This step is just to confirm that the Production logic is truly in sync with the working environments.
Hi Edwin Siruma,
This issue often arises when Production hasn’t fully picked up the latest plugin updates despite the module showing as current.
Try rebuilding and redeploying the app in Production.
Publish all dependent modules, particularly those using the File Viewer Plugin.
Production might still be caching old plugin code from before the upgrade.
The client actions are the same for the plugins in all environments. It is happening in all of our mobile app not just one mobile applications.
Rebuild, Published, Deployed several times even before I posted this question.
We are also getting the same error with the InAppBrowser plugin.
Thank you for all your replies.