Adobe AIR Development

[JRab]

whoahooo. i think u were also the one who mentioned we shouldnt bank on just one application and should submit a few. good thing you took your advice! hah. i guess the qnxstagewebview really was more like alpha rather than beta hah. good thinking!

[tags07]

You have a sharp memory, JRab. And I am really glad I took my own advice.. I have submitted 4 apps in all now working on couple of more...its getting to be addictive   

[UberschallSamsara]

@tags07 - So does the email from RIM imply that if your rejected app was the only one you had submitted, that you can't re-submit it after fixing it and still make the offer deadline?

Probably better to stick w/apps that don't depend on shaky API's though.

[tags07]

@UberschallSamsara:  I am not worried as much regarding the offer deadline..as I already got the tablet offer with my 2nd App. But I also want to resubmit the failed app after some rework using Webworks.  

I just wish the simulator would loadup fast and i can finish the testing and go to bed

[TheDarkIn1978]

---

tags07 wrote:

@UberschallSamsara:  I am not worried as much regarding the offer deadline..as I already got the tablet offer with my 2nd App. But I also want to resubmit the failed app after some rework using Webworks.  

I just wish the simulator would loadup fast and i can finish the testing and go to bed

---

i'm a bit concerned.

i'm sure i'm not the only developer who has spent the last several months perfecting one app, trying to complete it before the deadline.  i'm not using any of the QNX components or webservices, but you never really know what could go wrong during testing, especailly since we don't have access to do any on-device testing ourselves.  would we really not get a second chance if rejection happened after the deadline?  AFAIK this question still hasn't been answered.

i'm trying to fight the urge to spend a few hours whipping together and submitting some lame app now just so i don't have to pay for the device when they're released.

[UberschallSamsara]

That was the essence of my question.  If your only app is submitted before the deadline but fails testing the first time in the test house, for whatever reason, are you still eligible, as long as you fix the issues to where the app passes testing.  My impression is that the answer is yes (as long as you don't abuse them by just submitting junk), but it would be nice to get some clarity on the issue.

[tags07]

Hard to say what happens to apps that get rejected once the deadline completes. I'd think BB may honor resubmissions for those apps for a limited period. No reason not to give folks a chance to fix errors and resubmit. Just my speculation.

[peter9477]

I have no thoughts on all that, but I would suggest rebuilding the app that failed to function, using the latest SDK, and re-test on the latest simulator.

Especially if you were using QNXStageWebView, in December, when it wasn't documented, you inevitably risked problems like this, I think.

(Or did you already rebuild when 0.9.2 came out and that component was first documented?)

[peter9477]

As the Test House appears not to be interested in providing timely feedback in case of problems, my only option, aside from submitting a "crapplication" (as we call them in the IRC chat), seems to be to anticipate what problems they might be facing with my app.  It moved to testing on Feb 21 but to date I've heard nothing back.

Has anyone had an app approved that used SWIPE_START instead of SWIPE_DOWN?  If so, did you happen to base it on my own code, either as posted in the forum or using the state-machine-based code in my blog?

Has anyone had an app approved that used SampleDataEvent to generate sound?  This worked fine in 0.9.2, got broken in 0.9.3, and perhaps works differently in the real tablet.

Has anyone had an app approved that use the htmlText property of either Label or TextField, with embedded http: links, or which used the similar href="event:..." functionality along with an event handler to launch the browser using a navigateToURL() call?   (Yeah, that's a mouthful.)

These three things are the only things I can think of which may not work the same between the simulator and the real tablet, and which I used in my app.

[jtegen]

@peter:  So it has not failed testing, you're just concerned that it might?  Does the app work in the simulator (minus sound) as a normal user would expect?  Does the sound work fine in AIR?  It has only been a short time, so are you just getting nervous?

IF your app gets kicked back, I am confident you would be able to turn the issues around in a short period of time.

I think you're fine (until you hear otherwise of course).

Time to start working on your next great app.