Unexpected Error in Acceptance Nanoflow, but Works Fine Locally

0
Hello Mendix Community, I’m experiencing an issue with a few nanoflows I recently made in our application. In my local environment, everything works perfectly, but when I try to use the native app in acceptance or production, I encounter the following error:   "Fout Client [2024-11-12 10:15:28.039 ][6571731406251231] An error occurred while executing an action of AQ_Offline._Object_TemplateSelectie.actionButton1: Unexpected error occurred, please contact your system administrator. Nanoflow stack: "Switch" in nanoflow "AQ_Offline.AT_Object_TemplateSelectie" Current page: AQ_Offline._Object_TemplateSelectie Stack: @/var/mobile/Containers/Data/Application/03173609-1E19-43DF-90E7-9774A9E6750E/Library/Application Support/com.ippiq.aquinacceptatie/Ota/638630280253008717/index.ios.bundle:1027:1809 Me@/var/mobile/Containers/Data/Application/03173609-1E19-43DF-90E7-9774A9E6750E/Library/Application Support/com.ippiq.aquinacceptatie/Ota/638630280253008717/index.ios.bundle:35:19907 r@/var/mobile/Containers/Data/Application/03173609-1E19-43DF-90E7-9774A9E6750E/Library/Application Support/com.ippiq.aquinacceptatie/Ota/638630280253008717/index.ios.bundle:35:19612 V@/var/mobile/Containers/Data/Application/03173609-1E19-43DF-90E7-9774A9E6750E/Library/Application Support/com.ippiq.aquinacceptatie/Ota/63863028025...(trimmed)"   Can anyone point me into the right direction? Or is there a way to use a breakpoint in a nanoflow?   Thanks in advance!   Kind regards, Joey Field
asked
2 answers
0

This kind of error is hard to track, indeed ...

 

I'd try to compare the commit id number of the Acceptance/Production environment with the commit id in which the mobile application (IPA or APK/AAB) was generated.

 

If is different, it can be the root cause of your error.

 

In addition, try to build your app using the appstoreDebug flavor (instead of appstoreRelease) and inspect the LogCat to see if you catch any additional error related info.

answered
0

Hi,

Thanks for the help!

To solve the issue we needed to create a new build. This because the native template was updated.

answered