12-22-2010 01:01 AM
It does look like a problem with the manifest-- it approaches 1 MB right before it stops working. I've restructured everything and combined all my files into one large file and all is well again. I guess that many files was just a bad idea.
12-23-2010 11:45 AM
I just confirmed that not only does it result in "result::failure" if the manifest.mf is above about 1MB, but even with smaller manifests it doesn't really work.
I created a subfolder with between 1500 and 3000 files (one byte long) each with a 205-character filename. This resulted in manifest.mf sizes between 527680 bytes and 1054180 bytes. With the smallest one, the package could upload correctly ("result::success"). At 2500 files (manifest size 878680 bytes) it gave "result::" with no success or failure report. At 3000 files it reported "result::failure" consistently.
The thing is, even with "only" 1500 files, once the package uploaded the application would not start. Rather, I think it gets launched, but it never opens onscreen. All that happens is the app icon area slides down to show the "shuttle bar" (I think it's called that) and nothing. You can't launch any other app at that point either. It's either corrupted the system in some way, or some process is blocked trying to launch the app but it's taking too long to load (20 minutes and counting) or has died. The only process taking any CPU is pid #1. (Oh, and "pidin" shows that /sbin/launcher has died, so things are really kaput.)
So, word to the wise, there are some undocumented system limits and you should definitely not add hundreds of files to your .bar package or you risk problems.
12-23-2010 09:37 PM
Can you open a bug and submit your application as attachment? We can investigate what is causing it. Looks like some sort of limit.
I just added new issue https://www.blackberry.com/jira/browse/TABLET-35 to cover this, with reference to this thread and my above analysis.