-
Notifications
You must be signed in to change notification settings - Fork 821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppId mismatch failure in preview build of backend used across apps #13973
Comments
The same thing is happening to me. Is there any update? |
Hey folks, thank you for reaching. Could you provide us some additional on the reproduction steps? |
Hi @ykethan, thank you for checking. The situation is exactly what first comment and @felixpro describes. Just to clarify, it is as follows: OverviewWe have two apps: A and B. So repro steps would be:
short-term workaroundGoing to app > Hosting > Build Configuration > Build Image Configuration and pin the Amplify CLI version as Why workaround is not desirableWe need to pin the CLI version and never be able to catch up with the latest |
@felixpro @Ruci0094 thank you for the information. I was able to reproduce the issue by adding the |
Same as Ruci0094, amplify-meta is ignored in my repo. |
thank you for the confirmation on the gitignore. On a quick check with Amplify team, they suggest verifying your version control system as while the file maybe gitignored for any changes the file may have been pushed/committed to the repository previously. Additionally, if the file is indeed not present version control system would be happy in diving into the issue over a call. I am available on discord and my handle is |
Hey @ykethan I also added you on Discord. I confirm there is not meta file in the repo. |
Amplify CLI Version
latest (12.13.0)
Overview
We have several apps, assuming their appIds are
A
andB
.App
A
is not actively used anymore, but we still uses the backend resources associated to AppIdA
. Therefore, even though we interact withB
when we configure preview builds, our code'steam-provider-info.json
has appId =A
.With #13954, it started to fails with
AppId mismatch
which checks the appId from meta and appId from commandline.Questions
Considering it's possible to use Amplify backends across apps, I feel it's possible that
AppId
of the app on console does not match withappId
retrieved from metafiles (which is for backend, IIUC).Trace
The text was updated successfully, but these errors were encountered: