Flex Mobile 4.5 - Error: Could not resolve TabbedViewNavigatorApplication to a component implementation?

Any idea what swc or configuration might be missing? When making/running I get the error:

Could not resolve <s:TabbedViewNavigatorApplication> to a component implementation.

I'm trying to use the 10.5 EAP and opened a Flash Builder 4.5 mobile Flex project. This is the 4.5.0 SDK that Adobe handed out a few weeks ago at 360Flex.

Thanks

9 comments
Comment actions Permalink

As far as I see there are no public releases of the Flex Hero SDK that contain TabbedViewNavigatorApplication yet. The only publically available version of SDK with mobile components is 4.5.0.17689, but TabbedViewNavigatorApplication class appeared later. If you have more recent version of SDK with mobile components - pleasse add it as 'AIR Mobile SDK' at File | Project Structure | SDKs and use it for you module.

0
Comment actions Permalink

Thanks Alexander,

Yeah it's not "public" so much; I'd forgotten how old the labs release was. This is why you want to attend awesome conferences like 360Flex, so you can get early looks at what the Flex SDK team is working on. ;)

That's what I did to add the SDK. I get the code hinting/autocomplete, the mxml markup is recognized, and I can even click through to the component declaration in the mobilecomponents.swc, but I get that lone error on compile.

I'll try working with the SDK again and reading through the swcs and source to make sure I've got everything included. Of course, it works fine in Flash Builder, but I'd really prefer to stick with IntelliJ.

0
Comment actions Permalink

Please check different compilers available at File | Settings | Compiler | Flex Compiler.

By the way I hope this SDK release is not "secret" so much. Can you please upload it to our ftp server: ftp://ftp.intellij.net/.uploads/ This ftp is not visible from outside so you won't see your uploaded zip. IDEA 10.5 is close to release and we must be sure that it supports Mobile AIR applications development.

Thank you,
Alexander

0
Comment actions Permalink

Flex compiler change makes no dif.

Hope the updated version of the SDK helps you out.

As you are probably aware, June is the targeted release of the final 4.5 build and Flash Builder will also include iOS as a deployment option for both actionscript and Flex projects. Would love to have that baked into the IDE, however there's always ANT.

Thanks!

0
Comment actions Permalink

Thanks a lot!

Next IDEA EAP (expected tomorrow) will contain action to package .ipa installation file. Then it can be installed to iOS device via iTunes. The action is at Tools | Flex | Package Mobile AIR Application.
Work is in progress and feedback is always welcome!
Thanks again!

0
Comment actions Permalink

Awesome, looking forward to it! My Flex team got sick of hearing me talk about IntelliJ, so they all switched over. We love what you guys are doing, keep it up!

0
Comment actions Permalink

David, I tried to play with SDK 4.5.0.20967 and had no issues with TabbedViewNavigatorApplication highlighting or compilation. Please check SDK configured for your module once more. I guess it points to older SDK installtion.

0
Comment actions Permalink

I redid the SDK as an AIR Mobile SDK and it does work, thanks for the confirming that!

I think you may want to look at how IntelliJ sniffs out the SDK in use when adding a new Flash Builder project. This is what I did originally. IntelliJ asked me for the location of my project and then the location of my Flash Builder installation, and then wired up the configuration. Although the projects were Flex mobile AIR in Flash Builder, they didn't come over as such in IntelliJ.

Also, when choosing Run Debug > Main Class (descriptor will be generated) I got the following error:

error while loading initial content
Process finished with exit code 9


When switching back to my own app.xml descriptor it worked fine.


Thanks again!
0
Comment actions Permalink

Import mobile project from FB is already fixed in today's EAP. "error while loading initial content" is also fixed, but for the next EAP.

0

Please sign in to leave a comment.