Firebase-tools: [distribution] Requested entity was not found

Created on 7 Feb 2020  Â·  11Comments  Â·  Source: firebase/firebase-tools

[REQUIRED] Environment info


firebase-tools:7.12.1


Platform:macOS

[REQUIRED] Test case


When i try to upload my ipa using a specific appid i get an error although the appid exists
I run the following command
firebase appdistribution:distribute --app "1:696982949839:ios:c587f53961ad2c1df64cba" --release-notes 'test 1' --testers '[email protected]' Runner.ipa --debug
and i get
Error: App Distribution could not find your app 1:696982949839:ios:c587f53961ad2c1df64cba. Make sure to onboard your app by pressing the "Get started" button on the App Distribution page in the Firebase console: https://console.firebase.google.com/project/_/appdistribution

[REQUIRED] Steps to reproduce


As you can see i run a firebase apps:list and i get my 2 apps. Then i run firebase appdistribution:distribute with the exactly same appid for my ios app and i get the error. The android app uploads just fine.
image

[REQUIRED] Expected behavior


ipa should be uploaded to the firebase distribution

[REQUIRED] Actual behavior


ipa should isn't uploaded to the firebase distribution and i get errors
firebase-debug.log

Most helpful comment

For those that are facing this problem, a reminder: You need to press the "Get started" button twice (once for android and another time for iOS). I've spent a lot of time investigating this problem (because I did once for one platform) and figure out that I needed to do again for the other one ... terrible "UX" and for sure it needs improvements to avoid such silly error

All 11 comments

Did you follow the instructions in the error message? App Distribution must
be enabled before you can use the cli to upload builds.

On Fri, Feb 7, 2020, 5:15 AM Giorgos Papadakis notifications@github.com
wrote:

[REQUIRED] Environment info

firebase-tools:7.12.1

Platform:macOS
[REQUIRED] Test case

When i try to upload my ipa using a specific appid i get an error although
the appid exists
I run the following command
firebase appdistribution:distribute --app
"1:696982949839:ios:c587f53961ad2c1df64cba" --release-notes 'test 1'
--testers '[email protected]' Runner.ipa --debug
[REQUIRED] Steps to reproduce

[image: image]
https://user-images.githubusercontent.com/847472/74032442-a3435680-49bc-11ea-8f5f-777d2ee7975a.png
[REQUIRED] Expected behavior

ipa should be uploaded to the firebase distribution
[REQUIRED] Actual behavior

ipa should isn't uploaded to the firebase distribution and i get errors
firebase-debug.log
https://github.com/firebase/firebase-tools/files/4170915/firebase-debug.log

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/firebase-tools/issues/1963?email_source=notifications&email_token=AAAAH7V3NY7SK4Z7XGMEZFDRBVNG3A5CNFSM4KROKX72YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ILZZYCQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAH7WWPYCX32IMJQSOJ7TRBVNG3ANCNFSM4KROKX7Q
.

lots hours of continues working, so obvious

@mbleigh Is there a CLI way to enable App Distribution?
Reading the docs for Firebase CLI it uses CLI for all steps except this one GUI button we have to click in the console to enable distribution. I'm trying to automate a prototyping workflow for my developers, and this step is hanging me up. Maybe Fastlane can upload and enable distribution? Not sure, but Fastlane is too heavy for what little I need to do (i.e. upload a single .ipa file). Fabric was relatively simple; as long as the app was launched and the bundle identifier registered with Fabric, an .ipa could be uploaded. Firebase lets me register the bundle ID programmatically, and upload programmatically, but this one in-between step (which seems kind of unnecessary to me) cannot be automated?

Same for me i have a pipeline that using fastlane and bash commands that automates the builds, signing and distribution for every new app.

So there are 2-3 stoppers here

  1. Enable distribution
  2. Register SHA certificate for android
  3. upload notifications certificates for IOS
  4. connect google analytics

@ChristopherDrum I'm the PM of App Distribution. Enabling from the CLI is something on our roadmap and we want to add this. There are a few considerations we need to take into account that add a bit of complexity. I totally hear you that this would make initial onboarding a lot more seamless. I don't have a timeline to share right now, but this is an improvement we will be making.

@alexsinger is there any way to automate enabling of App Distribution for now?

@Sega-Zero not yet

I also had this:

{"error":{"code":404,"message":"Requested entity was not found.","status":"NOT_FOUND"}}

...error from the firebase CLI when it was GETing the details of the appID.

The "Make sure to onboard your app by pressing the "Get started" button on the App Distribution page in the Firebase console: https://console.firebase.google.com/project/_/appdistribution" message was confusing for me since I didn't have this button to press (I pressed it a while ago).

It turns out I got the error since I was using minimal "Advanced" permissions for the user doing the uploading, and I hadn't given it the "Firebase App Distribution Viewer" permission.

Could the CLI distinguish this situation from the more common not pressed "Get started" situation, and give a more specific error message? It looks like this might need extra support from the API.

For those that are facing this problem, a reminder: You need to press the "Get started" button twice (once for android and another time for iOS). I've spent a lot of time investigating this problem (because I did once for one platform) and figure out that I needed to do again for the other one ... terrible "UX" and for sure it needs improvements to avoid such silly error

@feharaujo
You're a lifesaver! I fell into the same pitfall.

@feharaujo I lived the same issue.

I have 2 apps with different packages inside of the same firebase project (two different flavours of the same app) and I lost a lot of time finding that theres a switch lust after App Distribution title where you change the registered apps and I needed to "accept" for each one.

Was this page helpful?
0 / 5 - 0 ratings