04-18-2011 03:53 PM
I submitted my application about 2 and a half weeks ago, shortly afterwards submitted version 1.1 following the Adobe builder 4.5 instructions. Today I have received a denial of my app because of lack of signing for both version 1.0 and 1.1. The latter should be signed. I'm going to try and go through the process from the beginning again (the form submission, etc) though I fear the worst.
Could someone let me know what I actually did wrong, or what was missing from the bar file?
Solved! Go to Solution.
04-19-2011 02:16 AM
same here, got the denial email. I examined my bar file and it is indeed signed. Moreover, there do exist such five meta files (RDK.SF, RDK.EC, MANIFEST.MF, AURTHOR.SF, AUTHOR.EC). I get confused.
04-19-2011 02:27 AM
04-19-2011 02:40 AM
no, i don't think re-submit it will still be eligible according to what the offer says.
by the way, the timing of denial is interesting, right before the launch date.
04-19-2011 03:28 AM
From what I hear from other developers in the forums it appears that you can still be eligible for the offer as long as the first submission was by the end of 31st March EST. There have been a few examples... I just hope that still holds.
I agree... a few hours before the launch date is the first feedback since submission a lot of us have had including myself.
04-19-2011 07:45 AM
If you can provide the application names I'll be able to determine the status of your applications.
Yes, the Free PlayBook offer only requires you submit before March 31 at midnight. You will receive a follow-up email regarding the PlayBook offer once your application is Approved, regardless of when it is Approved.
04-19-2011 08:03 AM
04-19-2011 09:05 AM
04-19-2011 10:01 AM
Thank you very much for taking a look at my issue, I've seen the confirmation emails now :-)
Does the Playbook offer mail come a little later?
04-19-2011 10:08 AM
FYI for others experiencing this problem.
I signed with an older SDK 0.9.1 which was rejected.
I then used the command line instructions provided by BlackBerry to sign using the updated sdk (1.0.2 I believe) and that was accepted.