Codemagic Build Stuck on Splash Screen

[yonycherkos]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

Flutter (Dart)

Steps to reproduce

Dear Codemagic Community,

We are currently building a Flutter app, and while the app works perfectly when run locally and has been successfully published to beta testers, we are encountering an issue with builds generated via Codemagic. Specifically, the build created with Codemagic gets stuck on the splash screen when launched on the simulator, while locally generated builds run without any issues.
The Codemagic-generated build gets stuck on the splash screen, preventing the integrated QA script from executing successfully. Notably, the QA script has been thoroughly tested locally and performs as expected. To further diagnose the issue, we installed the artifact generated by Codemagic on a local simulator and observed the same behavior—the app remains stuck on the splash screen.

We have checked for any configuration mismatches but have not been able to identify the root cause of this issue. The app works fine on the simulator when built locally and does not encounter this problem.
Could you kindly assist us in identifying any potential configuration or environment issues within the Codemagic workflow that might be causing this? Any guidance or troubleshooting steps would be greatly appreciated.

Thank you for your time and support. We look forward to your assistance.

Best regards,
Rejuve Team

Expected results

The build should install and launch successfully on the emulator, and the QA script should execute without any issues.

Actual results

The build was successfully installed on the emulator; however, the app failed to launch. Consequently, the QA script also failed, reporting an inability to locate the expected widgets.

Build id (optional)

67514d81a6c8951abdeacec2

[dam-ease]

Hello @yonycherkos,
From your logs, I see the first screen seems to be a login page and also can see an error in the integration test step:

MaxRetryError: HTTPConnectionPool(host='localhost', port=4723): Max retries exceeded with url: /session (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x106199fa0>: Failed to establish a new connection: [Errno 61] Connection refused'))

Can you please share more information about the first screen of the app and what functionality it has?

From experience, it generally occurs due to missing credentials, e.g., Firebase config files or some conflict with the libs added and another lib that were already in the project. Can you check this out? Also, do you have any error handling going on in your app either with Sentry of Firebase Crashlytics?

Also, a user shared a solution: https://stackoverflow.com/questions/56407299/where-to-save-googleservice-info-plist-in-flutter-without-xcode that worked in his case

[tksuns12]

I have a same symptom Build number is 674fa1ae20bf0debefdea73f.

It happens before MyApp is on, Sentry actually can't catch the problem.

[dam-ease]

Hello @tksuns12,
Thanks for sharing this!
Can you please share more information about the first screen of the app and what functionality it has? I see you are making use of firebase as well, there is a possibility there are missing firebase credentials in codemagic which results in a check on the first screen being blocked. Can you check out for your firebase credentials?

[tksuns12]

Actually I suspected one thing, which was that maybe an env variable has a typo because I don't know sometimes blank letter could be stuck in there. So I pasted a new value again ang it worked. It was totally my mistake. Thank you for help.

[dam-ease]

Glad this is resolved now!
@yonycherkos Please can you share if you have been able to check this out on your end as well?
Kindly let me know if you have any questions or concerns

[yonycherkos]

Thank you all for your responses. I successfully resolved the issue with the app being stuck on the splash screen by dynamically generating the .env file from the environment variable definitions.

However, we are encountering a related issue with the login and authentication flow. We are utilizing AWS Amplify for authentication and have double-checked that the environment variable definitions for the Cognito keys are correct.

Any insights or suggestions regarding this issue would be greatly appreciated.

Thank you!

[dam-ease]

Glad to hear this has been resolved on your end as well.
You can checkout this section of the official docs on headless authentication - https://docs.amplify.aws/gen1/javascript/tools/cli/usage/headless/ to see if it helps. Also kindly share more details on the exact issues you are currently facing or any error message so I could tailor my response.

[yonycherkos]

I am currently experiencing an issue with the Amplify cognito API. When attempting to log in using a valid email and password, I receive a "something went wrong" error message from the API. This issue does not occur in my local environment or local build, where the login functionality works as expected.

The problem occurs only to the build generated through Codemagic. I have ensured that all necessary Cognito keys are included in the environment variables list and have verified that they contain the correct values.

I would appreciate any guidance or insights you may have regarding this matter. Thank you for your assistance.

[dam-ease]

Hello @yonycherkos,
From the error message, I think this might still be related to configuration keys. Can you please confirm that all the relevant keys are present in codemagic. Also, check in with the values that there are no hidden formatting issues (like extra spaces or line breaks). Also, is it possible you enable detailed logging for Amplify to get more context about the error during login? Or an error reporting or network inspection tool to get full logs on this?

[yonycherkos]

Hello @dam-ease
Thank for your reply. I did double check that the environment variable definition are correctly. To make sure there are no any error in the environment variable, I just define the variables directly in the codemagic.yaml file by copy and pasting it from local .env file. However, this still doesn't solve the login or authentication error.

[dam-ease]

Hello @yonycherkos
Thanks for your response!
Two other things come to mind now. How do you make use of the .env file in your project, please can you share that. This is to confirm that your project gets access to these values. Also, I was checking out enabling logging to get more details on this error.
On another note, you have access to intercom, you can connect us via the Intercom widget from Codemagic Dashboard to get faster and dedicated responses.

[days155]

Hi!
I have the same issue.
IOS is working fine
Locally, the build is working,
Debug build with Codemagic is working
But the release build with Codemagic stuck on the first screen right after the Splash screen. No errors or exceptions were caught by Sentry or Logcat.
Build number is 675c6d17d6a90b1632c5f8d4

[days155]

Migrating to Flutter's Gradle plugins helped to fixed the issue

[yonycherkos]

Hello,

I resolved the Flutter Amplify login and authentication error by removing the --no-codesign command from my build process. Initially, I was using the command:

flutter build ios --simulator --no-codesign

However, I found that the issue was resolved when I updated the command to:

flutter build ios --simulator

I am not entirely sure how the --no-codesign option affects Amplify authentication, especially since my Amplify configuration was correct. If anyone has insights on this matter, I would appreciate your input.

Thank you!