Skip to content

Empty application after publishing it in iTunes Connect (Firebase related) #25167

Closed

Description

@timbergus

I'm pretty sorry for the lack of information, and I'm sure this is something I'm doing wrong, but I don't know where else I can ask. I have a pretty small application that shows a list of values from a static file. I uploaded it to iTunes Connect and downloaded it using TestFlight. Everything works just fine in my iPhone X.

I have modified the application to add a Firebase connection with a Firestore DDBB. If I run the application from Android Studio directly in my phone, it works, and it shows the data from the database. If I archive the app and upload it to iTunes Connect, and install it through TestFlight, when opening the application, it just appears as a white screen. The application works but shows nothing, but an empty white screen.

Do you know what is happening or how I can get information that can help to solve my problem?

Regards

Activity

  1. changed the title [-]Empty application after publication in iTunes Connect[/-] [+]Empty application after publishing it in iTunes Connect[/+] on Dec 10, 2018
  2. changed the title [-]Empty application after publishing it in iTunes Connect[/-] [+]Empty application after publishing it in iTunes Connect (Firebase)[/+] on Dec 10, 2018
  3. changed the title [-]Empty application after publishing it in iTunes Connect (Firebase)[/-] [+]Empty application after publishing it in iTunes Connect (Firebase related)[/+] on Dec 10, 2018
  4. vagrantrobbie commented on Dec 10, 2018

    @vagrantrobbie

    I've had this problem once before.

    I solved it by recompiling the app with a new version number and uploading it again to the App Store. It then worked as expected

  5. timbergus commented on Dec 11, 2018

    @timbergus
    Author

    I've tried the full process. New project using Android Studio, install pods, update pods, clean, build, and archive. The app has been released for testing a couple of minutes ago, and I have download it using TestFlight. Same result. As white as ever. Weird thing is that the app is not crashing, but neither showing an empty result from Firebase. It shows no app at all. Thanks for the idea though.

    And by the way. Thanks, everyone for Flutter. It's freaking amazing :)

  6. hartmannj commented on Dec 11, 2018

    @hartmannj

    Did you run flutter build ios --release before archiving?
    Additionally, in the docs following is mentioned:

    To ensure that Xcode refreshes the release mode configuration, close and re-open your Xcode workspace. For Xcode 8.3 and later, this step is not required.

  7. added
    platform-iosiOS applications specifically
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Dec 11, 2018
  8. added this to the milestone on Dec 11, 2018
  9. zoechi commented on Dec 11, 2018

    @zoechi
    Contributor

    Please add the output of flutter doctor -v.

  10. timbergus commented on Dec 11, 2018

    @timbergus
    Author

    Ok. This is my flutter doctor -v:

    screenshot 2018-12-11 09 44 10

    And about flutter build ios --release, I was doing the process using only XCode, and building and archiving throw the XCode menu options.

    This is the message after building:

    screenshot 2018-12-11 10 10 45

    This is the only message from XCode when archiving after flutter build ios --release:

    screenshot 2018-12-11 09 58 24

    And this is the only different decision from Objective-C to Swift that I did during the process. I left it by default.

    screenshot 2018-12-11 09 57 41

    And it's finally working 🎉It seems that the XCode process of clean, build and archive does not work properly. It is needed to run flutter build ios --release. Why is this? Could you tell me or point me to a reference where I can read about? I really want to understand the process.

    It seems to work for the two apps I'm developing right now. Thanks.

  11. zoechi commented on Dec 11, 2018

    @zoechi
    Contributor

    Might be related #24887, #24239, #24641

  12. timbergus commented on Dec 11, 2018

    @timbergus
    Author

    Looks like. So for the moment, we should use the full command line process and only the XCode IDE to archive and publish?

  13. rcunning commented on Dec 21, 2018

    @rcunning

    After banging my head against the same issue for a few hours, what seems to work every time is:

    1. XCode Product -> Clean
    2. flutter build ios --release
    3. XCode Product -> Archive

    One would think flutter could at least stop the archive with an error in one of its scripts in the case where you have not followed this undocumented procedure. Minimally, instructions at https://flutter.io/docs/deployment/ios really need to spell out that you must do the Clean step every time.

  14. github-actions commented on Aug 14, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  15. locked as resolved and limited conversation to collaborators on Aug 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    platform-iosiOS applications specificallytoolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions