I wrapped the application and it worked, but it doesn't seem to work
Closed this issue · 18 comments
We have already wrapped our packaged app and we have successfully wrapped it.
However, I heard a report from the client that MAM was not running properly, and I found that the wrapped app was different when the screen was turned on.
When I checked, a similar screen appeared for the Android-wrapped app. However, in the iOS app, this screen does not appear, only the version information is changed.
What more can I check? It doesn't seem to be controlled by the screen as well as the MAM policy. Unable to open document received from Outlook
Hey @songmw90 This screen wouldn't appear every time. If you are able to access you app, then it means the policies should have successfully applied. What issues are you seeing with the document?
If I directly install the Android wrapped app and run the app, it will appear like the screenshot above.
However, in the case of iOS, even when directly installed, it works the same as an unwrapped app. I think Android's execution plan seems to be right.
When transferring documents from Outlook to the app, it is assumed that the encrypted content in Intune is applied.
@songmw90 Could you send me logs as per this document: Logs for Wrapped Apps to vigavadi@microsoft.com?
The diagnostic console menu is present, but doesn't open when starting the app.
As a special note, intune wrapping fails in versions 14.x and 16.0. We tested it with a successful app on version 15.1.4
Hey @songmw90, does the diagnostic console not open even after turning the toggle on from the settings and then restarting the app?
Yes it is
@songmw90 Couple of questions:
- Would you be willing to share the unwrapped ipa to vigavadi@microsoft.com? I could try to wrap it on my end and check if there are any issues?
- For 16.0.0, do get any errors while wrapping?
- Could you share a video of your experience after you have installed the app on your device?
We had success with the wrap tool version 16.0.2. (Before that, wrapping failed at all)
But still the first screen is the same, even with all options enabled, the console doesn't open
Is the above request still valid?
No, it was not resolved. it's late night here. I will prepare the report tomorrow and send it to you.
I've emailed you the resources you requested.
The email address is songmw90@naver.com. Titles that start with [#80]
I've attached the original ipa and the ipa we created via 16.0.2.
I've also attached a video that shows the console not showing up.
@songmw90 Thanks for the info, this is really helpful for debugging issues. One follow-up question, does you app support scenes or does your application still rely on the AppDelegate to manage the single window object? If your app is not configuring scenes, could you remove this from your Info.plist file and try again?
We are currently on Saturday. The code is at the company, so I'll check it out after the weekend and let you know. However, our app has been maintained since iOS5. So, as far as I know, it doesn't use scenes, it uses AppDelegate .
The Application Scene Manifest (Generation) value of our app is No for both debug / release.
As you said, when I deleted the column and wrapped it, the first screen changed and the console appeared properly.
However, we can't delete this option right away because we don't know what effect it will have on our app. Is this issue going to be supported by the wrapping tool or should we delete the column?
@songmw90 Great to know that it worked. We'll work on a fix for this. But in general, if your app doesn't use scenes, then removing UIApplicationSceneManifest shouldn't be any problem. The UIApplicationSceneManifest is only useful if you have the UISceneConfigurations dictionary set. You can refer to the Apple Documentation for UIScenes
The app works, but crashes. There was no crash in the old version.
I sent the log and video by e-mail, so please check