Skip to main content
bcvincent
Participating Frequently
November 6, 2014
Answered

Flash CS6 Air to iOS "Edit Application Settings" menu not coming up. No way to publish to iOS.

  • November 6, 2014
  • 18 replies
  • 15275 views

Using a freshly re-installed and updated Flash CS6 on a 64-bit Macbook OS X 10.9.4.   I've tried various combos of Air 3.2, 3.4, 14, and 15, since yesterday, and I'm getting the same result.  Just two days ago everything about this setup was working flawlessly.  I was compiling and pushing Air apps to my iPad for testing.  Early yesterday morning I tried this and got a message that I didn't save, but was something along the lines of "This installation is not setup for this process" or something.  Since then, when I click on the wrench to bring up the Edit Application Settings menu, nothing happens.  This is true if I click on it next to target in the properties pane, or if I go to Air to iOS Settings from the File dropdown menu. 

The other strange part of this is that if I open some older projects, I can get the menu to come up again. But on the project I was working on it doesn't.  And if I create a new, blank FLA file and go straight to settings, it also doesn't work.  And if I attempt it and it doesn't work, if I close the file that wasn't working it crashes Flash completely. 

It seems like some database or cache is corrupt but I did a full uninstall (using adobe cleaner) and reinstall, and it's still happening.  I found one old thread on google about this same problem, and the solution given was to delete Library/Application Support/iPadApp/Local Store/appDB.db, but I don't even have this file to delete. 

Pretty much can't produce my content like this so I'm a sitting duck.  Any info would be greatly appreciated.  This is my first post here so I apologize if I'm missing something.

This topic has been closed for replies.
Correct answer tommybanana1967go

very interesting. apple developer support were happy to engage with this and checked out all my certificates and stuff and updated some stuff in Xcode.

but while doing it i discovered that if you move the provisioning profile somewhere else eg a new folder, then you can open the Edit Application Settings  and then add the provisioning profile from the new location and

flash publishes successfully.

at least  that is a workaround - although a pain in the arse!

18 replies

Ramy__
Participant
November 17, 2014

The replace by an older provisioning profile worked the first time but after 2 days i'm facing again the same issue, the application settings popup not showing.

This is so annoying, does anyone have a solution for this on mac

I'm not able to compile iOS apps anymore.

Inspiring
November 17, 2014

check my replies above. there is a pretty easy workaround.

Participant
November 12, 2014

Anyone tried using AIR 16 SDK? Have to try it yet.

Inspiring
November 12, 2014

to be clear you need to move the provisioning profile somewhere new each time. you cant move it for example back and forth between two folders. that  doesn't work. But if you make a new folder and move it into there it will all work fine. I do notice that since this behaviour started Flash cs6 is les stable and crashes intermittently.

Inspiring
November 11, 2014

having exact same issue. updated provisioning profile. same process as all year ( done it 50 times this year....).

then suddenly wont open edit application settings and then flash cs6 crashing.

actually did a whole load of stuff ( rebuild directory and permissions, reinstall;ed flash cs6.... took ages

then found this and after reading this thread I deleted the provisioning profile.

suddenly started working again.

going to try and download provisioning profile again and see what happens.

Inspiring
November 11, 2014

yes it is definitively the provisioning profile. using an old one is no go for me - I need to add new testers.

I am currently on the phone to the apple developer program support - see what they say.

really dont want to upgrade to flash cc,,,,

tommybanana1967goCorrect answer
Inspiring
November 11, 2014

very interesting. apple developer support were happy to engage with this and checked out all my certificates and stuff and updated some stuff in Xcode.

but while doing it i discovered that if you move the provisioning profile somewhere else eg a new folder, then you can open the Edit Application Settings  and then add the provisioning profile from the new location and

flash publishes successfully.

at least  that is a workaround - although a pain in the arse!

Participant
November 11, 2014

I installed Flash CC and now everything works.

Very annoying that I had to do that. And if this is Adobe's way of forcing people to upgrade (just speculating) then they are running a very shady business.

kvand67
Participant
November 11, 2014

Hello,

Have the same problem with new provision profiles

Reported this bug Bug#3850040 - Flash CS6 crash

Also to open the «Edit Application Settings» menu you can replace a new provision profile with any older one.

When all settings are done, to compile a project change to the new provision profile again.

Thank you

bcvincent
bcvincentAuthor
Participating Frequently
November 11, 2014

Latha, I did figure out from your link the work around about the direct publishing bug.  Putting the first version of my project on the iPad via iTunes then allows for further publishing directly to the iPad.  As for the main problem, upgrading to Flash CC is not an option for me right now. 

kvand67,  "you can replace a new provision profile with any older one"  What do you mean by this? 

kvand67
Participant
November 11, 2014

Hello

If you need to open the «Edit Application Settings» menu, instead of creating a new project, you can copy and paste another provision profile(from any project) instead of the current one (which causes the problem), run Flash, open your project, open the desired menu, change necessary settings.

Then you can put your original provision profile back and publish.

Just temporary deleting provision profile (file) doesn't solve the problem in our case.

Participant
November 10, 2014

I have the same problems as well. Same thing happens on 3 different projects on two different versions of flash (cs6 and cs5.5) on two different computers.

I can put in my certificate and provisioning profile once and then the settings menu won't open again no matter what I try. Reboot, new .fla file, etc.

Seems to be a computer issue so something must be stored somewhere on my computer to prevent it from working again.

bcvincent
bcvincentAuthor
Participating Frequently
November 10, 2014

"Seems to be a computer issue so something must be stored somewhere on my computer to prevent it from working again."

That appears to be the case, although it's an issue that is being created because of the certificate/provisioning profile or because of Flash's reading of those files.  I've recreated this same issue on a different computer and using a different project, but with the same new certificate. 

Participating Frequently
November 10, 2014

Usually when flash gives you the error, "Please check if there is enough space on the device." it's because there is some sort of mismatch with the profile and or developer certificate or information in the -app.xml is not the same as in the provision profile.

Apple recently had a new user agreement that I had to log in and approve. Every time they do that I end up having to go to my keychain, and delete my local developer certificate, re-download it from apple and make a new p12.

After doing that I find it also helps to some how edit the provision profile to force it to update and then download that fresh too.

Are you using the Air 15 SDK?  I have not tried using that yet with what I have done above.

Adobe Employee
November 10, 2014

Hi ,

seems this problem is file specific ,if file  is created , saved with old provisioning profiel and ceritificate and opening with new profile might causing some issue , If possible can you please share your fla files with us ? 

Thanks!

Latha

Inspiring
November 10, 2014

Hi Latha,

Actually, I managed to work around it by using Flash CC. It seems like the problem exist only with older versions of Flash (I used Flash CS6 until now).

Theres not much I can share because it relates to the .p12 or provisioning profile but you can easily try and reproduce it by doing the following (on Mac):

1. Create a new Flash CS6 project.

2. Create a CER file from apple's members center and convert it to .p12 using keychain access.

3. Create new provisioning profile  using the new certificate.

4. download both and use use them when publishing your Air for iOS app.

Now what will happen for you after that I'm not sure. For me on the first time (when I updated the locations to the new .p12 and provisioning profile and the application settings menu is still open) it says that me certificate is expired as if it kept trying to fetch the old certificate and not the new one.

Once I close the settings window I can never open it again with that project file (Also if I change it to another version of Air for iOS). But if I try to change it to Air for Android I can still open it.

Taking the same file and opening it in CC does allow me to open the application settings menu, though.

Thanks,

Oz

bcvincent
bcvincentAuthor
Participating Frequently
November 7, 2014

Still no fix but some further info.  My Apple Dev Certificate expired a couple of weeks ago, and I got a new one and that's what I've been trying to use. 

I tested this out on my older Macbook.  On this same FLA that wasn't working, I could get to the Edit Application Settings menu initially, but when I put in the new certificate and new provisioning profile info and hit OK, I could no longer get back into that menu. 

There also seems like there's some memory of what happened last, because if I go directly from this problem to a new file, I get the same issue.  But if I open one of the older working projects and open the settings menu, then create a new file, I can get into the new file's settings menu. But whenever I try to get into the settings after the new provisioning profile info has been updated, I get locked out. 

It seems like it has more to do with the provisioning profile than the certificate.  I can alter the certificate info in the settings menu without causing this problem.  When I change the provisioning profile, that's when I can't get back into the menu.  This is a huge problem because I have all new profiles using the new certificate and can't publish any of my work.

Participating Frequently
November 7, 2014

I'm having the exact same issue.  Looks like you have found more information on it that I have.  I have lost a whole day trying to figure this out.

bcvincent
bcvincentAuthor
Participating Frequently
November 7, 2014

Did your issue just start?  Does it also involve new certificates or profiles or is it completely out of the blue?  If it's a profile issue it could be a change Apple made recently, if not I don't know what the deal is. 

The last time it crashed out on me I got the Adobe error popup, and I sent in the report, and it said Adobe had found a solution - "click here for more info".  It was just a link to adobe.com.  Helpful...