iOS App Crash on Launch

[List0734]

Priority/Impact

High (critical issue, blocks workflow)

Description

App Version: 1.8.4
Last Known Working Version: 1.8.2
Device: iPhone X
iOS Version: 16.7.11

Description:
The wger app crashes immediately upon launch. The app opens for a brief moment, then closes unexpectedly without displaying any content or error messages.
Frequency:
Every launch.
Severity:
High – app is unusable.

Server version

No response

Mobile app version

1.8.4

[rolandgeider]

(Moved issue to the flutter repo)

@peter9teufel do you have any idea what this could be or how we could debug it?

[peter9teufel]

@rolandgeider Did 1.9.0 inteoduce changes in the server that might cause the issue?

[rolandgeider]

not really, not. Also, regular server api changes(or other errors) would mostly just cause that "an error occurred" popup to show

[rolandgeider]

I just saw that this happened with 1.8.4, does the error also occur with 1.9.0 @List0734?

[List0734]

I’m not seeing a 1.9 version of the app in the AppStore, is there an App TestFlight where it may have been been published? I don’t believe this would be a server issue as I reinstalled the app during troubleshooting as such it should have no server configured.

[peter9teufel]

Version 1.9.0 has been approved today, if you check again you should already see it in the App Store.

BR,
Peter

[peter9teufel]

Have you been able to test it with the latest App Update (Version 1.9.0)? And one more question, are you using a self hosted instance of wger? If yes, is the wger instance up to date?

Best regards,
Peter

[List0734]

I installed the latest app version, and unfortunately that has not resolved the issue. I recall this issue starting around the end of May but had to take a break from using the app. I am using a self-hosted instance of wger that is up-to-date. As the app has not been configured however, I fail to see how the server version could be contributing to the issue.

[List0734]

Is there a way that you know of that I would be able to grab logs from the app crash?

[peter9teufel]

I can see in the details of your initial Issue that you are on iOS 16.7.11 which is likely the cause of the issue as this indicates that you are on a rather old device that does not support iOS 17.

@rolandgeider i checked the minimum iOS versions in the referenced libraries and some of them require iOS 17.

camera_avfoundation-camera_avfoundation_privacy:: 12.0
camera_avfoundation:: 17.0
flutter_keyboard_visibility:: 17.0
flutter_zxing:: 17.0
Flutter:: 13.0
image_picker_ios-image_picker_ios_privacy:: 12.0
image_picker_ios:: 17.0
integration_test:: 17.0
package_info_plus-package_info_plus_privacy:: 12.0
package_info_plus:: 17.0
path_provider_foundation-path_provider_foundation_privacy:: 12.0
path_provider_foundation:: 17.0
Pods-Runner:: 17.0
pointer_interceptor_ios-pointer_interceptor_ios_privacy:: 12.0
pointer_interceptor_ios:: 17.0
rive_common-rive_common_privacy:: 12.0
rive_common:: 17.0
shared_preferences_foundation-shared_preferences_foundation_privacy:: 12.0
shared_preferences_foundation:: 17.0
sqlite3_flutter_libs:: 17.0
sqlite3:: 12.0
url_launcher_ios-url_launcher_ios_privacy:: 12.0
url_launcher_ios:: 17.0
video_player_avfoundation-video_player_avfoundation_privacy:: 12.0
video_player_avfoundation:: 17.0

a workaround could be to reduce the min iOS version in the Podfile for all Pods to an iOS version below 17 (e.g. 16 or whatever the minimum target should be), maybe worth a try.

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
    target.build_configurations.each do |config|
      config.build_settings['ENABLE_BITCODE'] = 'NO'
      config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '16.0'
    end
  end
end

Best regards,
Peter

[List0734]

@peter9teufel I am indeed on an older device that does not support iOS 17. I just applied the change you described in a fork and sideloaded the resulting app. It appears functional as the app now launches. I will continue to use the app and let you know if any issues occur. As sideloading apps tends to be a hassle, would this change be applicable to a release version in the AppStore?

[peter9teufel]

@List0734 can you make a pull request with the changes that fixed it for you or do you want to integrate and check this by yourself @rolandgeider ?

BR,
Peter