AppId mismatch failure in preview build of backend used across apps

[Ruci0094]

Amplify CLI Version

latest (12.13.0)

Overview

We have several apps, assuming their appIds are A and B.
App A is not actively used anymore, but we still uses the backend resources associated to AppId A. Therefore, even though we interact with B when we configure preview builds, our code's team-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 with appId retrieved from metafiles (which is for backend, IIUC).

• When backend is used across apps, is it WAI that this error is thrown or does it come from our misconfiguration? Any idea on where to fix?
• I assume removing appId from commandline can be a workaround but I'm not sure where we configure that. Do you have any pointer?

Trace

2024-10-10T14:01:17.716Z [INFO]: �[0mAmplify AppID found: <APPID OF APP B>. Amplify App name is: <APP NAME OF APP B>�[0m

2024-10-10T14:01:17.770Z [INFO]: �[0mBackend environment stg found in Amplify Console app: <APP NAME OF APP B>�[0m

2024-10-10T14:01:19.921Z [WARNING]: - Fetching updates to backend environment:XXXs from the cloud.

2024-10-10T14:01:21.503Z [WARNING]: - Building resource api/XXXX

...

2024-10-10T14:01:24.592Z [WARNING]: ✔ Successfully pulled backend environment XXX from the cloud.

2024-10-10T14:01:25.190Z [INFO]: ✅

2024-10-10T14:01:27.372Z [INFO]: 🛑 Amplify appId mismatch.

2024-10-10T14:01:27.372Z [INFO]: Resolution: You are currently working in the amplify project with Id <APPID OF APP A>
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

[felixpro]

The same thing is happening to me. Is there any update?

[ykethan]

Hey folks, thank you for reaching. Could you provide us some additional on the reproduction steps?
Are you running into this when associating an existing backend app to a frontend app using the console branch edit button?
https://docs.aws.amazon.com/amplify/latest/userguide/reuse-backends.html#reuse-backends-edit-existing

[felixpro]

The problem is related to the preview generation. They were working fine and suddenly started throwing an error.

In my case, I have two apps, and App A uses the backend from App B. For some reason, the PR previews for App A stopped working due to the error. 🛑 Amplify appId mismatch.

Here is the error:

[Ruci0094]

Hi @ykethan, thank you for checking. The situation is exactly what first comment and @felixpro describes. Just to clarify, it is as follows:

Overview

We have two apps: A and B.
We use app B to trigger preview deploy of frontend for Github branch.
However, our team-provider-info.json has AmplifyAppId = A because we use the backend associated to the app A.
It has been working fine until recently, but suddenly deploy preview started to fail with AppId mismatch. It corresponds with the release of 12.13.0

So repro steps would be:

1. Create initial app A
2. Create second app B and Follow https://docs.aws.amazon.com/amplify/latest/userguide/reuse-backends.html#reuse-backends-create-connect to connect to backend of app A
3. Set up deploy preview of app B
4. Trigger deploy preview and it fails

short-term workaround

Going to app > Hosting > Build Configuration > Build Image Configuration and pin the Amplify CLI version as 12.12.6

Why workaround is not desirable

We need to pin the CLI version and never be able to catch up with the latest

[ykethan]

@felixpro @Ruci0094 thank you for the information. I was able to reproduce the issue by adding the amplify-meta.json file to my git repository.
Could you confirm if the repository currently does have the amplify-meta.json file present under the amplify/backend?
to note the amplify-meta.json should be .gitignored, refer to the amplify-meta and .gitignore documentation providing this information.

[Ruci0094]

Could you confirm if the repository currently does have the amplify-meta.json file present under the amplify/backend?

No, amplify-meta.json is .gitignored so we don't see that file in the repo. I assume it is generated in the build of deploy preview, maybe?

[felixpro]

Same as Ruci0094, amplify-meta is ignored in my repo.

[ykethan]

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.
tried reprod

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 ykethan