Some time ago on the twitter feed of @as3lang you could see this thread
And then recently on Adobe Forums you coudl see this other thread
AIR 28 SDK - Error message received from Apple
After submission of an app compiled with AIR 28 SDK, I receive the following message:
Missing Asset Catalog - Your app is missing the asset catalog file in 'Dis moi !.app'.
Does anybody know how to solve this issue?
Thks in advance for your answers.
after someone point out to the latest AIR SDK 28 beta
Yes I did, but since i'm working with Flash Builder on a Windows platform, it does not help me.
Would you pls know how to solve the issue within my working environment?
And this is exactly why you should test on real targets.
Sure, it sucks, if before you could produce an iOS app from Windows, and then you can't do that anymore.
But you should not rely on this convenient feature (from the AIR SDK) forever, because Apple will change their rules and it will break things, iOS 11 and the
Assets.car are a perfect good example of that.
Don't be a whiny little kid, even if Adobe AIR team try its best, even them sometimes can not necessarily fix that kind of problem for you.
Apple does expect developers to use a mac to produce iOS apps and as soon as you do use a mac (or equivalent like a VM or hackintosh) many things become much simpler to do.
Also, there are many options: from macOS running in a Virtual Machine, to buying and "old" mac mini, to using a hackintosh, and as a dev publishing to different platforms you owe to your users to actually test your app on all those platforms.
So, it is just my opinion, but here how I see things, take what you want from it.
I do plan to build on iOS 11 and for the iPhone X but in my case it is out of question to shell out $1000+ for the device itself just to test on it.
I also don't like remote debugging with a friend eg. "Can you please test this app on your device please?".
Also in my case, I don't build only mobile apps for Android and iOS, I also build desktop apps for Windows and macOS.
In fact, it is a bit worst than that because I also publish an open source project where I need to support macOS.
Even if I completely refused to own a mac (hardware), I would still spend plenty of money on RAM, because running VM require more RAM.
But there is also what I believe and know work best:
- spending as much money as possible to have a big juicy workstation
with tons of CPU, tons of RAM, tons of screen, tons of HDD, etc.
- knowing your target as good as a user using this target on a daily basis,
otherwise you will produce crap software for that target, and worst,
you can not support your users if/when they have problems (using your software on that target).
- anything that make me not waste time is good, and I would rather use that time
to improve the quality of the sofware produced
- you don't get something for nothing
Ultimately, it is a bit counter-productive to go against the flow, if Apple expect to have a mac to produce iOS apps then just go with it, the same way if you need to produce a Windows desktop installer you can not do that from a mac you will need to get a Windows either hardware or VM, it is a bit useless to complain and fight about it.