Cannot wrap in version 15.0

[songmw90]

/Volumes/IntuneMAMAppPackager/IntuneMAMPackager/Contents/MacOS/IntuneMAMPackager -i {NAME}.ipa -o {NAME}_wrapped.ipa -p {origin}.mobileprovision -x \<array>\<string>/Users/admin/Desktop/intune/{extra}.mobileprovision\</string>\</array> -c "{CREDENTIAL}" -v true -e

I have been wrapping in 14.0 with the same command, but after migrating to 15.0, I cannot wrap and a segmentation 11 error occurs.

When I tested it several times, it seems to be a provisioning profile problem, but what builds in 14.0 does not build in 15.0 despite the same profile.

When I put the profile used in -p in the argument in the test when I put it in the -x argument, only IntuneOpenInAction warning is displayed and the build works.

I upgraded Xcode to version 13, is it impossible to build at all in wrapping tool 14.0?

[songmw90]

At first I tried to do it, but it was too difficult. Crucially, we're not making apps for the purpose of intune wrapping. It is trying to wrap for customers who require intune wrapping. In answer to the last question, yes. (see screenshot)

Is there no other way?

[gastaffo]

@songmw90 Did the wrapper work when the single icon? If so than it would appear to be with the website.

[songmw90]

No it's not work. same error

[gastaffo]

@songmw90 Can you send me the ipa with the single icon in it? I would like to debug that one as it should be a bit simpler

[songmw90]

just sent.

[gastaffo]

@songmw90 I found a possible fix for the issue however the person who originally wrote the code is on vacation and won't be back until monday. I will talk to them on monday on why the code is set up the way it is and how we should fix it. If we do find a fix it would most likely be release in January 2022.

[songmw90]

Okay. I'll be waiting

[gastaffo]

@songmw90 After more testing we have found that the icon files in the IPA are being corrupted somehow when being exported. So long term solution is to find a way to generate them that doesn't use those websites. A good quick test to see if the file is corrupted appears to be attempting to open it in GIMP as it wouldn't open those files.

However we did notice that if you open the image in Preview, then export it as a PNG, that exported file is no longer corrupted. So a possible quick solution could be to go to your icon xcasset folder and open each icon file in preview and export it using preview. We did that with the icons sent that were crashing and afterwards the crash did not occur. Would y'all be able to try that?

[songmw90]

Are you saying that if I don't use the website and make assets one by one using tools such as Photoshop, there will be no problem?

[gastaffo]

@songmw90 Thats what we are finding. You could use the website and then use preview to export the images again which could be a little bit faster than using photoshop manually.

[songmw90]

Are you saying that it doesn't work when I build using a single 76x76 icon rather than an imageset? Why don't you give me a sample of an image that "works well"?

[gastaffo]

@songmw90 It has something to do with your icons themselves. For example this picture of a giraffe does not cause a crash.

Also if we take on of the icons y'alll provided and then export them through preview that does not crash. However y'all are creating the icons being put into the app is causing them to become corrupted images.

[songmw90]

I think I've figured out the problem. Starting with iOS 5, to register an icon, it was put in the info.plist, not the asset set. In our app, there were icons registered in info.plist, and there were also icon asset sets. (I don't know which icons worked as actual icons. It seems that they are all included in the app)

After you gave me the image, I tried to delete all the assets, but the wrapping failed and I thought it was strange. So I looked for it. I found out that the icon was registered separately in info.plist. So, when I wrapped all the icons after completely deleting them, it was successful.

However, this is a test when everything is deleted, and tomorrow I will register an actual asset set and build it and report the result. I want to inform you of the results quickly. But I have deleted too many parts of the project for this test, so I have to restore it first.

[gastaffo]

@songmw90 Awesome good to here we might have a solution!

[songmw90]

I found something really weird. If there is nothing 'transparent', the wrapping seems to fail.

In the two attached icons, transparency is added to the upper left corner, and the wrapping result is different depending on the difference between not and not. It only succeeds when there is transparency. (The added transparency is named _trans)

Apple forbids transparent icons, so why does this happen when wrapping? Do I have to add transparency when creating icons in the future?

[gastaffo]

@songmw90 Interesting. I will have to keep that in mind while investigating on our side. It could be that adding anything transparent causes it to have an alpha channel.

I thought apple only forbid transparent store icons?

We haven't really seen this issue before so we will keep looking into it on our side but if you do run into this issue again adding an alpha layer to the icon would be a quick mitigation.

[songmw90]

As you said, it is forbidden when uploading to the Apple Store, but it is not a problem to follow the guidelines and create icons. We just made the icons as a guide.

We are also making icons with transparency. But I don't think it's a complete solution to this issue. I hope you solve the issue

[gastaffo]

@songmw90 It is interesting that we were able to avoid the crash by reexporting the icon through preview without adding any transparent items in general. How did you make these non-transparent icons? Are they originally from JPEGs? Also it is interesting that the icons that were causing the crash were labeled as corrupted by GIMP?

[songmw90]

As far as I know, the only file that can be used for iconset is png. We made up the icon set from undamaged, intact files. To be honest, I don't even know what you mean by damaged and I don't understand. I can open the file and it looks fine.

Do you also have a sample app? Try removing the alpha channel by completely filling the transparent parts of the giraffe image with color.

Then build the app and try wrapping it. If giraffes are bothering you, you don't need to. Try the two icons I attached. Do you think it will happen right away? They are 'uncorrupted' files as you say

[gastaffo]

@songmw90 We were able to open the file in preview but GIMP told us it is corrupted.

[gastaffo]

@songmw90 Didn't you generate the icon set from a JPEG? Also we need to do the alpha channel as Open In action extension icons are transparent. I think apples requirement might only be for the App Store icon not the icon in general.

[songmw90]

Even if it is a png, if there is no transparent area, there is no alpha channel. The icon set is made with png.

What I understand is that the extension is a transparent icon with no image, but if it is a transparent icon, why not just create a transparent image randomly in the wrapper? Why is the app icon affected?

And although I am not going to upload it to the App Store, there are many icons other than us that do not use transparency. It's not that we're weird. We just filled in the icons without any blank space.

So please, forget the binary I sent and try it with the attached icon.

I already did the wrapping test. The transparent ones are wrapping and the non-transparent ones are not.

The only difference between the two is the one transparent pixel on the left. I've provided two samples for you to troubleshoot

If you say that the icon must be transparent, you can edit the document to say that it is a specification. Then I follow.

However, since you call the current situation an 'issue', I keep commenting and I am providing information so you can solve it...

[gastaffo]

@songmw90 A PNG can have an alpha layer yet no transparency. Consider this image I got by exporting one of the icons via preview. It has no transparent pixels yet it has an alpha layer.

The issue in our code appears to be with having no alpha layer. However we aren't sure as the icon images causing the crash behave oddly compared to other PNGs so we don't necessarily know. There may also be an issue with our code however that will take longer to fully figure out. Also it can sometimes take a while for a fix to be released.

I would recommend finding a way to add an alpha layer to the icons either by adding the transparent pixel or by exporting via Preview so that y'all aren't blocked anymore while we investigate our code further.

I was curious about the JPEG becuase y'alls source image is a JPEG and its possible whatever tool y'all used to generate the icons didn't correctly convert from JPEG to PNG.

We need to read the app icons becuase the wrapper uses them as a template to generate the icons for the IntuneMAMOpenInActionExtension, which is used so that the app will be able to receive files from other apps, and we attempt to make the icon look similar to the original app icon.

[gastaffo]

We do appreciate all the information and help you have provided with this issue.

[gastaffo]

Also as a heads up I will be out of office from tomorrow until 2022-1-17. So while I am out @hhawkins can help if y'all need anymore help.

[songmw90]

We've had this problem for too long. I will proceed with wrapping with a transparent image. We will continue to cooperate.

[gastaffo]

@songmw90 Was using the transparent image able to unblock y'all and your customers? If y'all want more help we can set up a call to talk about the issue. Due to this issue being quite niche we think using a different icons, such as the one with a transparent pixel or by exporting the icon via Preview is the best solution as of now.

Let me know if y'all need any more help.

[songmw90]

We built the icon with a transparent 1 pixel, and distributed it this week. There does not seem to be any problem with the operation of the app. I also agree that inserting a transparent 1 pixel into the icon is the best option. However, since there is no way for general users to know about this part, I wondered if it would be better to fix the simple "segment error". I don't mind closing the issue as this has been fixed.

[gastaffo]

Closing the issue. If you need any more help feel free to reopen it and ask. Thanks for being patient with us.