This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 30%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECM%3C/text%3E%3C/svg%3E)
We have developed a MS teams app (manifest version 1.13). When opening the app on M365 iOS, we get presented with following error message. This only seems to happen on M365 iOS, it works for Android and also on all the other Microsoft Mobile apps.
This [2400] also occurs if our teams app backend is not even running.
We figured out, that this behaviour is caused by having a "webApplicationInfo" section in the app manifest.json. Removing it, resolves the 2400 error.
"webApplicationInfo": {
"id": "{{APPLICATION_ID}}",
"resource": "api://{{APPLICATION_ID}}"
}
We need this section to authenticate the teams app backend with MS GraphAPI.
Selecting "Cancel" will close this dialog and display the teams app as expected. The next time the app is opened, the error appears again.
We tried side loading the app and also an org rollout via setup policy.
Happy for support, this issue is currently blocking our teams app submission to the teams store, thank you!
Correlation Id: 5839f1db-e400-394c-be0b-ca9e5ebb7a5e
Timestamp: 2024-03-11T18:46:12.000Z
DPTI: D7F00B9A-86D2-4575-A6B9-388984D9C862
Error Tag: 49dvr
Error Code: 0
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 50%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVP%3C/text%3E%3C/svg%3E)
Hello Christian Moser,
Can you try inserting the ngrok domain url in the following format and see if it works-
"webApplicationInfo": {
"id": "{{Microsoft-App-Id}}",
"resource": "api://{Base_URL_Domain}/{{Microsoft-App-Id}}"
},
Thanks a lot, it seems now also to work for m365 iOS changing it to the suggested format. I wonder why since we defined the registered app application id Uri on Azure portal like the following: api://{Microsoft-App-Id} without the {Base_URL_Domain} but we are still able to use MS graphApi from the app backend.
Hello Christian Moser,
Can you please confirm if your issue is resolved?
I have to come back to this. The error 2400 only disappeared on m365 iOS app once we removed the complete section
"webApplicationInfo": {
"id": "{{APPLICATION_ID}}",
"resource": "api://{{APPLICATION_ID}}"
}
Just changing the resource string did not resolve it in the end, probably the app with the removed webApplicationInfo section was still cached in m365 app.
@Vaibhav Pandey (Admin) @Vaibhav pandey Please escalate this internally, m365 iOS does not seem to handle manifest.json with webApplicationInfo section correctly.
yes it did, thanks for you support! I posted a question with our findings. It did not in the end, testing on staging failed.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 53%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVM%3C/text%3E%3C/svg%3E)
This issue is being tracked by Engineering team here. You can refer this thread for furthur updates.