I have mac and xcode if you need help no problem
> On 16 Feb 2018, at 14:16, bilbosax wrote:
>
> No, it has more to do with this note published by Adobe. On page 3 under "iOS
> SDK Upgrade", you will read that to publish an App for iOS using AIR 28, you
> now need access to a Mac with Xcode insta
No, it has more to do with this note published by Adobe. On page 3 under "iOS
SDK Upgrade", you will read that to publish an App for iOS using AIR 28, you
now need access to a Mac with Xcode installed to create an Assets.car file
that you can then use to package with your swf. This is a major pain
Possibly related?
http://blogs.adobe.com/flashplayer/2018/02/running-adobe-flash-builder-on-mac-with-java-78.html#sthash.UQ7rrxjt.dpbs
Thanks,
Om
On Thu, Feb 15, 2018 at 10:20 PM, bilbosax wrote:
> My concern had something to do with Assets.car I believe I read, losing
> icons, and other issues
My concern had something to do with Assets.car I believe I read, losing
icons, and other issues when trying to release using AIR 28.
--
Sent from: http://apache-flex-users.246.n4.nabble.com/
Greg, you are the man!! Upgrading to AIR 28 did the trick and I no longer
have these annoying artifacts. And now I am aware that I should read the
release notes.
But I still have the concern as to whether I will be able to submit an .ipa
to the App Store that was compiled using AIR 28 in Flash B
Greg, thanks for the heads-up on that! I will definitely look into this. I
am currently using AIR 27, so that could be a real possibility. I only have
one big concern with upgrading to AIR 28. I have read somewhere that you
can't use Flash Builder to export a final release to be deployed on iOS
It might pay to check your AIR version and release notes:
E.g. for example
https://helpx.adobe.com/flash-player/release-note/fp_28_air_28_release_notes.html
under FIXED ISSUES:
[iOS]Artifacts are observed when child Sprite is near bottom of
screen(AIR-4198445)
There have been things like this i
... and if I remove my custom skin with the green in it, I still have the
artifacts in the same shapes and sizes, but the artifact changes to the
color of the default MobileGridHeaderSkin. So it is related, but I don't
think it is the cause.
--
Sent from: http://apache-flex-users.246.n4.nab
It's clean as a whistle if I do that. I haven't quite put my finger on it
exactly yet but I think it might in PART be related to the
MobileGridHeaderSkin that I created for the MobileGrid. It is not 100%
related to this as it does not explain the first picture I attached with the
pixelization in
What happens when you put that button in a blank application and run it?
On Feb 15, 2018 7:15 PM, "bilbosax" wrote:
> I have removed all of the custom components that appear in the various
> states
> of my app so that I have only the one component remaining. I removed all
> of
> the display obj
I have removed all of the custom components that appear in the various states
of my app so that I have only the one component remaining. I removed all of
the display objects from the remaining component besides the two buttons I
created, and I am still having the problem. I am at a total loss.
I
Hel!! Hahaha! I have been working on this annoying thing for two days
and have gotten nowhere!
I have a "next" button with a custom fxg button skin in the lower right
corner of my iPad app. It is inside a custom component that includes a
MobileGrid, a "previous" button and a label, and nothi
12 matches
Mail list logo
