Vorschläge aktivieren
Mit der automatischen Vorschlagsfunktion können Sie Ihre Suchergebnisse eingrenzen, da während der Eingabe mögliche Treffer angezeigt werden.
Beenden
Flipline
Engagiert
Flipline
Engagiert
Aktivität
Apr 18, 2018
08:09 PM
Good to see that removing the "beta-reports-active" entitlement does indeed fix this issue. Amrita Gangwani any idea when a new release of AIR will be ready that stops this bug of automatically adding the "beta-reports-active" entitlement to adhoc builds? As others have mentioned, this was introduced in the the most recent release last Tuesday, and no previous version of AIR automatically added this to adhoc builds.
... Mehr anzeigen
Apr 16, 2018
08:55 PM
Unfortunately Linkage does generate classes/code, if you check out a SWF or SWC in something like FlashDevelop you can see that adding Linkage to a MovieClip calling it "testclip" is creating this class behind the scenes: package { import flash.display.MovieClip; public class testclip extends MovieClip { public function testclip (); } } One thing you could try is to have a separate SWF for each element (instead of using Linkage on multiple clips in the same SWF), with a separate xml file you load that keeps track of all of the filenames for those SWFs so you know what you need to load. Obviously that's much more cumbersome and slow depending on how many elements you need to load, but it might work in a pinch if you can't find any other ways around it.
... Mehr anzeigen
Apr 10, 2018
05:23 PM
2 Empfehlungen
If you don't want to use Xcode to generate the Assets.car file, you could try this website which generates an Assets.car file for you: Generate ios、android app ICON and Assets.car online You'll need to include that Assets.car file when you build your ipa, the same way you include your launch images for iOS. I seriously doubt they'll be updating older versions of AIR to fix this issue, because starting this month Apple now requires all new apps to use the iOS 11 SDKs and support iPhone X resolution, which is only possible with AIR 28 or 29 (and which requires Assets.car for all future builds).
... Mehr anzeigen
Mär 28, 2018
05:50 PM
We've used Heyzap (now re-branded as Fyber) in our AIR apps, they have an ANE and support mediation so you can include other networks like AdMob and UnityAds and a handful of others as well using the same SDK: Ane Setup and Requirements Docs • Fyber It's pretty good for interstitials and rewarded videos, though the Fyber and UnityAd networks are heavy on advertising apps where you seem to earn per install rather than impression/click for those. It supports banners now as well, but you'll probably want to add another ad network through their mediation to get a decent fill rate on that, I think AdMob and MoPub are the main options for banners.
... Mehr anzeigen
Jan 15, 2018
08:00 AM
2 Empfehlungen
Having the same problem here, and kind of figured out where this bug is coming from: If you have multiple layers affected by the Clipping Mask, if any of those layers have visibility turned off, you can no longer control-click any of the masked layers above that one that has the visibility turned off (but can usually control-click masked layers that are BELOW the one with the visibility off). Definitely a bug with Photoshop, and really messes up my workflow. Really annoying having to pay a monthly subscription for software that we can't use and have to constantly downgrade until updates are eventually rolled out.
... Mehr anzeigen
Nov 01, 2017
11:53 AM
You may also want to make sure you're bundling launch images for that specific device size when you're creating the IPA file -- if the app doesn't contain a launch image with a specific name and resolution, iOS will use a lower resolution and just scale up the content itself. I believe the one you need to include is "Default-414w-736h@3x~iphone.png" for it to recognize it should use the full resolution on a 6/7/8 Plus, otherwise it'll go with the the lower resolution like you mentioned, and report that lower value for screenWidth / Capabilities.screenResolutionX, etc.
... Mehr anzeigen
Sep 18, 2017
02:16 PM
I haven't tried this myself (still on an earlier version here), but I did see this article talking about the iTunes change: https://lifehacker.com/what-to-do-now-that-you-can-t-sync-ios-apps-using-itune-1809941947 It's from an average-user perspective rather than for developers, but this part jumped out as a possible workaround: Since you can’t manage the apps using iTunes interface, you’ll have to use your computer’s file explorer alongside the iTunes window. Plug your iOS device in your computer, find the actual app file, and simply drag it on top of your device when it shows up in the iTunes sidebar. You can use the same method to manually add ringtones and books. Sounds like you can possibly drag the app .ipa from your PC into the iTunes window and drop it on the device in the iTunes sidebar, seems a little convoluted but it might be worth a shot to see if this is possible?
... Mehr anzeigen
Aug 09, 2017
10:58 AM
When using the new "Export Image" in Animate CC 2017.5, there are problems with how it's treating transparency in the exported image. In the screenshot below, I have some graphics with transparent glass panels, which are made using pure white (#FFFFFF) at different opacities. In this preview from Export Image, you can see all of the transparent glass panels look to be shades of black or gray instead of white. Even if transparency is turned off, these pure-white graphics and still tinted black/gray because of their transparency: This example is using pure white, but even if I try a different color (like #FF0000 at 50% opacity), it will still look like a dull dark red as if it's lowering the R G B channels as well as the A channel. I've also noticed the same effect when I try to export solid colors in PNGs using Export Image -- all of the anti-aliasing around the edges of the artwork will be shifting towards black as it lowers its opacity for anti-aliasing, so if I'm trying to export a few pieces of artwork to composite elsewhere, everything will have a subtle black halo around it because of the RGB channels shifting towards 0 as the Alpha channel moves towards 0. If I use the "Legacy" export I don't have this issue, and if I export Movie as a PNG sequence it looks correct too, but the new Export Image feature is sadly not usable because of this issue with transparency. Has anyone found a workaround for this? Matte and interlacing don't seem to affect it, and even switching to the "Original" view shows this same issue with transparency, as if they were low-opacity black instead of low-opacity white. EDIT: For more evidence of the issue, here is a file where I made a few vector boxes of pure white, with different levels of opacity. Using Export Image, I moused over the middle box with is 50% opacity, and you can see the R G B values reading as 127 (following the A channel), rather than 255 like we'd expect:
... Mehr anzeigen
Okt 25, 2016
02:20 PM
2 Empfehlungen
I ended up making a standalone sticker pack with XCode, haven't tried to bundle one with an AIR app yet though. From what I can tell based on un-zipping that standalone ipa, the sticker pack bundle is located in a "PlugIns" folder within the Payload directory, so maybe it's possible to make the app extension in XCode and then copy it over to an AIR app -- not really sure what else would be involved in making it work though.
... Mehr anzeigen
Okt 25, 2016
09:48 AM
It seems that XCode has also switched to using integer, we just recently did a sticker pack with the newest XCode and the Info.plist it generated has integer here instead of number. Since XCode is now using integer, that's probably what they're expecting for all new submissions and why it's sending the warning message.
... Mehr anzeigen
Okt 19, 2016
09:06 AM
Agreed, it's clear this is an upcoming change for Apple where they strictly need integers here instead of strings, and there's no telling when this will be an absolute requirement and how this may affect things for new and existing apps. It doesn't seem to break anything yet (from what others have mentioned), but who knows, an upcoming iOS update may require integers and may ignore any apps with strings as "incompatible" with that device. I'd love to see a compiler update from Adobe on this fairly soon, especially since this is regarding the critical value of whether a device can even install an app.
... Mehr anzeigen
Okt 13, 2016
09:38 AM
Has anyone published live apps to the App Store after receiving this warning, and confirmed that it can be purchased/updated by both iPhone and iPad? Not really concerned about TestFlight, just worried about an actual release. I did attempt to change my app xml to "<integer>1</integer><integer>2</integer>" instead of "string", but adt gave me a warning and failed to compile. Not sure what else is going on under the hood, but it would be great if Adobe could release an update for adt that allows integer instead of string here.
... Mehr anzeigen
Okt 13, 2016
09:00 AM
Does anyone know if this "not compatible" issue only applies to TestFlight, or will this happen from a live app in the App Store as well? We have an update ready for a universal app that also got this warning in Application Loader, and we're not sure if we should push this live or not. It did show up as a valid build under Activity > iOS Builds, and it does show Device Family: "iPhone / iPod Touch, iPad" for that build.
... Mehr anzeigen
Sep 16, 2016
07:37 AM
Apple recently released iMessage "Sticker Packs" with iOS 10, which can either be delivered as standalone apps for the iMessage store, or can be bundled as an Extension within an iOS app. Bundling the stickers within your app is in interesting feature, since your app users will automatically get the stickers when they download or purchase your app. From what I understand, making the sticker pack is fairly straightforward with Xcode, but I'm not sure how to bundle it with an app created with AIR. Is there any current way that AIR supports bundling iOS App Extensions when creating an ipa? Or are there any plans for this? It sounds like the sticker pack would be packaged in the main app's ipa, but outside of the Payload directory and in its own folder structure. Documentation is a bit scarce, but here are some related links from Apple's site: Sticker Submissions - App Store - Apple Developer iMessage - Apple Developer (specifically the "Building iMessage Apps > Extensions to iOS App > Sticker Pack Extension" part)
... Mehr anzeigen
Aug 29, 2016
02:56 PM
Thanks for the update on this, I've been doing some more testing and have an update on what's happening: When I didn't specify ~ipad or ~iphone for my launch images, I was having this issue with the Retina iPad (with the file called Default-Portrait@2x.png) --- it launched to a black screen, and the launch image briefly flickered as the app finished loading. Once I added iPhone-related images and added "~ipad" to all of the iPad launch images, the image now correctly shows for Retina iPad. I also have more information about iPad Pro not using the correct resolution: If my launch image is titled "Default-Portrait@2x~ipad.png", I'm only receiving the lower resolution of 1536 x 2048. If I remove the ~ipad part and simply call it "Default-Portrait@2x.png", it does correctly run in the higher resolution of 2048 x 2738! I'm still trying to determine if I can include both launch images (one with ~ipad and one without), and if that will have any effect on the other resolutions or iPhones/iPods.
... Mehr anzeigen
Aug 25, 2016
12:19 PM
Hello, Could you please try this test again with "requestedDisplayResolution" set to "high" in the app xml? It sounds like you're running in standard, since Capabilities.screenResolutionX and Y were 768 x 1024 for you. When set to "high", our experience is that an iPad Retina (which has 1536 x 2048 resolution) won't show any launch image in this case (but will run at high res), and that an iPad Pro will choose the correct launch image but will not actually run in that extra-high resolution. If it's choosing the launch image of 2048 x 2738, shouldn't screenResolutionX and screenResolutionY be 2048 x 2738 as well? When we test with requestedDisplayResolution set to "high", we are getting 1536 x 2048 as the screenResolutionX and Y on iPad Pro, instead of the full resolution of 2048 x 2738 on iPad Pro. I can send a sample application if you're seeing something different with resolution set to "high". Thanks!
... Mehr anzeigen
Aug 18, 2016
08:28 AM
Sure, here are the launch image sizes I'm using, and what I'm seeing in two different scenarios. This is a universal app, so there are launch images for both platforms included: - Default~iphone.png (320 x 480) - Default@2x~iphone.png (640 x 960) - Default-375w-667h@2x~iphone.png (750 x 1334) - Default-414w-736h@3x~iphone.png (1242 x 2208) - Default-568h@2x~iphone.png (640 x 1136) - Default~ipad.png (768 x 1024) - Default-Portrait~ipad.png (768 x 1024) - Default-Portrait@2x~ipad.png (2048 x 2732) The app is packaged with the latest AIR 22, set to only run in Portrait orientation, and tested on devices running iOS 9.3.x. 1) When I test on an iPad Pro, the app is running at 1536 x 2048 (despite none of the launch images being sized for that). 2) When I test on an iPad with Retina display, I don't see any launch image at all, though the app does run at 1536 x 2048. If I only include the largest launch image (Default-Portrait@2x~ipad.png at 2048 x 2732) it does correctly use that resolution on the iPad Pro (though the iPad with Retina still fails to show any launch image at all), but once I've added these other launch images it doesn't work.
... Mehr anzeigen
Aug 11, 2016
10:02 AM
Will there be any updates to fix issues with iPad Pro launch images to support its native resolution, rather than the device running the lower 2x Retina resolution? To clarify, here are the issues: 1. Adobe mentions to resize the @2X~ipad images to be the native resolution (2048x2732), which does work if you include no other launch images, but this does not work if you also add a Default~ipad.png to handle standard-resolution iPads. When you do this, the iPad Pro reverts to normal iPad Retina resolution (1536x2048). 2. If you resize the @2X~iPad for the higher iPad Pro resolution, the other Retina iPads will not show any launch image at all. The Retina iPads would normally use this 2x launch image, but since the resolution doesn't match it just ignores the launch image completely. This happens regardless of any other launch images you add. Again, Adobe's solution only works if you don't want any launch images for any other resolution/device besides the iPad Pro. This is happening in the latest release AIR 22.
... Mehr anzeigen
Mai 31, 2016
02:09 PM
We've been having the same problem for years as well, but frustratingly it's not even consistent when using the same type of device, and seems to be happening to some users and not for others. We've had users who had this issue on an iPad 2 with < 900MB of free space, and when we try to duplicate it on our own iPad 2 (same iOS version, only leaving 100MB of free space, etc.) we couldn't duplicate it. And meanwhile there are plenty of iPad 2 users who don't have a problem with the SharedObjects -- but there are a bunch who do. Same goes for other iOS devices, some people have problems with iPhone 5 and some don't, some had trouble with iPad Mini and some don't. We haven't been able to duplicate it on any of our own devices, but plenty of our users have had this problem. Once we advise them to make some free space it will start working again, but the amount of free space they need also doesn't seem consistent. Some users get it to work around 500MB of free space, other users keep having the problem until they clear 1.5GB of free space. It's very frustrating, and even more frustrating that it's so hard to reproduce!
... Mehr anzeigen
Mai 13, 2016
08:48 AM
I was looking through past Release Notes for Adobe AIR updates, and found this in the 12/8/2015 release of AIR 20 under "Fixed Issues": [Android] [User Issue] App crashes while playing .flv videos on Nexus 7 in GPU render mode, working fine in auto and CPU mode. (4059244) Was the fix for this issue simply disabling GPU render mode on the Nexus 7? If that's the case, it's causing problems for other apps that previously used GPU render mode without a problem.
... Mehr anzeigen
Mai 11, 2016
10:44 AM
1 Empfehlung
Does anyone know if there is a list of devices that no longer support GPU render mode (especially ones that previously did support GPU render mode)? Since we have to update our older AIR 18 apps to AIR 21+ because of the Google Play OpenSSL issue, we've been testing our updates and noticed that our apps which use GPU render mode were suddenly playing terrible on some of our test devices. It seems they are instead running in CPU mode on some devices. I posted about this on the other Adobe AIR forum yesterday: GPU Render Mode not working on Nexus 7 with AIR 21+ The Adobe docs say that the Release Notes will list devices that have GPU rendering disabled, but the Release Notes don't seem to have anything about this here. Is there a list available for devices where Adobe has dropped GPU render mode support in newer versions of AIR? This will definitely be important moving forward, since I'm sure users are going to start requesting refunds for apps that suddenly play terrible on their devices after the updates, and we'd like to keep track of which devices are affected so we know whether there is a valid claim for a refund or not.
... Mehr anzeigen
Mai 10, 2016
01:26 PM
2 Empfehlungen
All of our apps are using GPU rendering mode (not direct mode -- they use the traditional DisplayList), and I'm noticing an issue when trying to update older apps made in AIR 18 to AIR 21 or 22. When testing on the Nexus 7 tablet (original 2012 version), app performance is terrible after updating to AIR 21 or AIR 22, when it was previously as smooth as can be using AIR 18. It seems that GPU rendering mode is no longer working on this device, since it's performing more like the CPU mode. In Adobe Scout, I see a large amount of time each frame (45ms+) devoted to "Rasterizing edges" and "Copying to screen", when these were never even mentioned when profiling in AIR 18. Under "Session Info > Machine" in Adobe Scout, with the AIR 18 app I see "GPU Vendor", "GPU Renderer", "GPU Version", etc. listed on this tab. When checking the AIR 21 or AIR 22 app, none of this data is shown (only CPU info). Does this device no longer support GPU mode for some reason in the newer versions of AIR? We never had a single problem with GPU mode on this device, so I'm not sure why this would no longer be working in the newer versions of AIR. Unfortunately, we're forced to update all of our Android apps to AIR 21+ because of the OpenSSL issue, so there's no option of leaving the AIR 18 apps in place. Is there also a list somewhere detailing which devices no longer support GPU mode (especially ones that previously did, but no longer do)? The documentation only mentions to check the release notes for devices that don't support it, but there's no information in the release notes pertaining to this.
... Mehr anzeigen
Mär 31, 2016
01:36 PM
Nice! Same here. Glad we don't have to worry about that now
... Mehr anzeigen
Mär 31, 2016
01:13 PM
I think when that error happened last time, they were claiming the AIR app had an earlier version of OpenSSL than it actually had. This time it looks like the version they're requiring is legitimately newer than what our AIR apps have --- my AIR 18 apps have 1.01m and they're looking for 1.01r or 1.02f (not sure if AIR 19 or 20 or 21 did bump it up to 1.01r since then).
... Mehr anzeigen
Mär 31, 2016
10:48 AM
Same warning here, I believe all of our apps listed in the email were using AIR 18, and we haven't released any apps with a newer version since then. Has this been in addressed in 20 or 21?
... Mehr anzeigen
Mär 12, 2016
02:13 PM
I'm also disappointed to see this is still an issue with Windows, though I've heard packaging still works fine on AIR 18 and AIR 19, is this correct? It's surprising that the older versions can still package correctly, and it's just newer versions of AIR that are unable to do so. Is this related to AIR 20 and 21 using a newer iOS SDK? By the way, thank you for shedding some light a little on what's happening regarding Apple verification changes -- up until now Adobe hasn't been very forthcoming about this issue's cause, so we haven't even known why this became an issue. I think for a lot of us, being able to publish on Windows is a critical issue to our workflow, and the only feedback we've seen is it being noted inconsequentially in release notes as a "known issue" along with minor things and never actually addressed.
... Mehr anzeigen
Feb 18, 2016
07:41 AM
Has there been any progress on the Windows side of this for packaging? We mainly work on PC, and have been holding out for a workable PC solution to this instead of having to change our production/development pipeline. It's been two months now that PC is unable to publish for the App Store, does it seem like a solution is coming in the near future? Or is there some underlying issue that's preventing it from working on PC at all? I'm not really clear on what the root of this issue is, if it's something that changed on Apple's side with iOS 9 requirements or if it's something on Adobe's side with changes to AIR 20. Also can anyone confirm that older versions of AIR (18 or 19) are still able to package and submit to the App Store? Not sure what we would be missing out on by using an older version (aside from iOS 9 API and SecureSocket API), but it would be a relief to know there's still an avenue to the App Store in the meantime. Any insight would be appreciated, thanks!
... Mehr anzeigen
Sep 28, 2015
07:47 AM
Just noticed that with Apple's latest update to iTunes Connect, there is a new section under "Pricing and Availability" called Bitcode Auto-Recompilation containing this message: Occasionally, we may automatically recompile apps that include bitcode to improve hardware support or to optimize our software. The checkbox below allows you to disable auto-recompilation for your app. What happens if you disable bitcode auto-recompilation? Your app or a thinned version of your app may be unavailable for some devices. Your app, and any app bundle that includes this app, may become unavailable whenever apps must be recompiled. If your app is unavailable on the App Store, Universal Purchase, redownloads, and Family Sharing won't work unless all platform versions have been approved. To maintain your app's availability on the App Store: Upload a new build of your app that contains bitcode. Test the new build with TestFlight (optional). Submit that build with a new app version to App Review. Reading further in their documentation about this, it says that bitcode is optional for iOS apps but required for Watch and TV apps. Does anyone know if AIR includes bitcode in our apps?
... Mehr anzeigen
Sep 21, 2015
07:32 AM
I've added this to the bugbase with steps on reproducing the issue here: Bug#4060581 - TOUCH_END not occurring when dragging outside in iOS 9
... Mehr anzeigen
Sep 18, 2015
11:16 AM
We're seeing an issue with dragging outside the stage in an AIR app in iOS 9 in a specific scenario: - App is only available for iPhone and not iPad (UIDeviceFamily is 1) - App is being used on an iPad, which scales that iPhone app up using its 1X / 2X compatibility mode - iPad is using iOS 9 In our app, we have a scrolling panel of items, where users can drag this panel left and right to see more items within. Under previous versions of iOS, when the user made an extreme swipe where their finger went outside the bounds of the game (or onto the bezel outside the screen), this would fire a TOUCH_END event. In iOS 9 however, it seems this touch event is just completely lost once their finger goes outside the bounds of the app window, and a TOUCH_END event never fires. Continuing the motion and dragging that finger back inside the screen and releasing after this happens will also not fire a TOUCH_END event. This is especially problematic when dealing with multitouch, as we keep track of a touchPointID when doing a startTouchDrag on that panel, and listen for a TOUCH_END where the touchPointID matches the ID that started the drag. Note that this seems to ONLY be occurring in the scenario mentioned above: an iPhone-only app being used on an iPad under compatibility mode, and only on iOS 9. This issue is not occurring on iPad-only or Universal apps (the TOUCH_END is correctly firing when dragging out-of-bounds for those). Also the same issue is occurring with no MOUSE_UP events being fired as well -- though this isn't as much of an issue as missing the TOUCH_END with its touchPointID for correctly handling multitouch events. I'm not sure if this is an issue on Apple's end with changing the behavior of touch events in iOS 9, or if it's an issue on Adobe's end with interpreting the touch events being sent in iOS 9. If anybody has any insight on if this is an AIR issue or an Apple issue it would definitely be appreciated.
... Mehr anzeigen
- « Vorherige
- Nächste »
Copyright © 2025 Adobe. All rights reserved.
AdChoices