Office library not loading for iOS 17.4 about office-js

[neprasad-microsoft]

Hi @tallain-rivaengine
We tried on iOS 17.4 with Outlook 4.2414 and were not able to reproduce the issue. Can you help us with the following queries for further debugging?

1. Are you able to run any other add-in?

2. Please capture the logs and send it to us . Instructions on how to collect logs - https://github.com/OfficeDev/office-js/wiki/Collecting-log-files-for-Outlook-Add%E2%80%90ins-issues

3. Please add a try catch in office.initialize and print the error in catch and let us know the error.
   Office.initialize = function (reason) {
   try {
   console.log(Office.initialize(): Huzzah!);
   }
   catch(ex){
   console.error(Office.initialize(): Error! ${ex});
   }
   };

4. Is this add-in published? If not, can you share a manifest which we can use for testing?

[YmaRivaEngine]

Hi @tallain-rivaengine We tried on iOS 17.4 with Outlook 4.2414 and were not able to reproduce the issue. Can you help us with the following queries for further debugging?

1. Are you able to run any other add-in?
2. Please capture the logs and send it to us . Instructions on how to collect logs - https://github.com/OfficeDev/office-js/wiki/Collecting-log-files-for-Outlook-Add%E2%80%90ins-issues
3. Please add a try catch in office.initialize and print the error in catch and let us know the error.
   Office.initialize = function (reason) {
   try {
   console.log(Office.initialize(): Huzzah!);
   }
   catch(ex){
   console.error(Office.initialize(): Error! ${ex});
   }
   };
4. Is this add-in published? If not, can you share a manifest which we can use for testing?

1. Are you able to run any other add-in? Yes
2. Incident ID: EQS9NX52
3. copied the code, and there are no logs printed in the try and catch
4. Yes, we are working on a sample manifest but we are afraid that cannot replicate easily

I am not sure if this will help things clear, but to give some background and the usage.
we are using this as part of the graph non-Sso fallback flow for the mobile device
Office.context.ui.displayDialogAsync(myloginUrl)
myloginUrl is an action method that gets the graph configuration on the server side and redirects the user to the MS AuthorizationRequestUrl, after the user inputs the credentials in the ms356 login prompt (hosted by the child dialog), it will redirect to a callback URL that contains the auth code, (the callback URL is configured in the Azure App Service), the callback URL will hit our action method, that rendering the view along with the auth result, inside of this view page, there is only the code that does Office initialization and Office.context.ui.messageParent(authResult)
we tried to remove Office.context.ui.messageParent(authResult), only keeping Office initialization and logs, as well as the test code, but it never hit the logs. And there is no exception in the parent or any events.
This flow worked for 2 years but stopped after IOS was upgraded to 17.4. IOS 15 and all Android platforms work as before.
We came out with a workaround that set the auth result in the localstroge. but we found the diag. close() in parent won't close the diag, no exception or event was captured. And this is also happened only in IOS 17.4 and above.

[DivyaPatidar]

@YmaRivaEngine Can you try one of the display dialog samples for Outlook and let us know if it works on iOS 17.4 for you?