Hey there, BT community! I've made the leap to Android. October 1st marks the "1-year anniversary" of my first iOS app. A year later, I'm trying to get a long-awaited Android version out in the market. I've run into a couple of speed bumps - any help on these issues/questions would be greatly appreciated! (using 3.0) 1) I installed Adobe Reader on the emulator. However, when I click on open document (for my selected PDF), I receive the error message: "path is not valid". What's up with that? 2) Ultimately, I'd like for the PDF to open within the app. Is this possible through the "Intercepting Menu Taps" how-to guide found here: https://www.buzztouch.com/files/howtos/intercepting-menu-taps.pdf ?? 3) On that last note, when I try to implement the code, "activityname" is not recognized and I received the following error: "activityName cannot be resolved to a variable". Possible solutions? 4) Launch images - where do I place them, what should they be named... and what sizes? 5) Screenshots - are you allowed to alter screenshots (i.e. add text/graphics) to submit to the Google App Store? What sizes do you suggest the screenshots should be? I realize that I've asked a lot of questions. Any help would be greatly appreciated in lending a helping hand towards submitting my first Android app! Thank you! :) -Nicholas

In essence, the PDF troubles are my main concern. Launch images + screenshots would be helpful once this technical issue is resolved. Thanks again for any help whatsoever! -Nicholas *EDIT* How does Android treat Word documents? Possible to read them? Better off converting to PDF?

The word, excel, pdf, and possibly the HTML plugin use the Android's native app to open/view. Typically what will happen is this: You include a word/excel/pdf plugin. In the plugin control panel, you designate a document, either local or dataURL When the plugin opens (in the app), you are presented with a button to 'open' document. At that time, the user chooses the native app they wish to use to view that document. They have a choice to use that app by default, or only one time. It's up to the user for that decision. Afterward, the chosen native app will display the document. If the user chose 'always' then it shouldn't ask them again. That's how it's supposed to work, anyway... it seems like (in BT Android v3) the HTMLDoc plugin will also exhibit this behavior. Cheers! -- Smug

Thanks for the info, Smug! Is there a reason that the emulator fails to open the PDF documents? Should I be concerned in received that message? And any thoughts regarding the "Intercepting Menu Taps" how-to guide? I just want to make sure that I'm actually implementing what I think it implements... which I believe to be the ability to open the PDF without exiting the app and opening it in another. Thanks again, Smug! P.S. PDFs are being stored locally -Nicholas

With respect to 'path not valid' that means it can't find your document. It either isn't being included in your package when you test it, or the dataURL is not correct. Make sure it's added correctly to the project (the file copied correctly to your project and the project knows it's there) or test the dataURL with a web browser or some other method. On the 'menutaps' excersize, If it's BT v3, then the Android format is going to be different. In BTv2.0 everything was centered around an 'activity'. Now with BTv3, we're centering around 'Fragments', which makes everything very similar, but different enough to make you want to pull your hair. Fortunately I'm already bald. Although it's no guarantee, instead of using 'thisActivity' try using "getActivity()" instead. However, sometimes converting Activity Code to Fragment code can be a little involved; it may take much more than this. Can't be sure. Good luck! Cheers! -- Smug And for PDFs, you will ALWAYS require a native app to view it; unlike iOS there is no intrinsic helper in the code.

Thanks, Smug, I'll try and figure that out. Everything seems to be where it should be in regards to my PDF documents and I don't see how they wouldn't be included in the app compilation... Also, just to make sure, the Intercepting Menu Tap guide that I'm trying to implement, its purpose is to do just that, right? Make the PDF open through the native app within my app without having to open in a new app? (woah, I used the word "app" a lot in that sentence). Thanks again, will test tomorrow! -Nicholas

I've never worked through the document, so I really don't know what it's for, other than to teach how to intercept menu-taps. I do know that since time eternal (at least within buzztouch time) on Android, you have always required Adobe or some compatible app to open PDF. It doesn't work like iOS, where the app opens the document. In Android, the user will have to choose a helper app to view the PDF, and will take them out of the app. I'm not sure if they can return simply, although the back button should allow that. I just keep away from PDFs in my Android, if possible. Cheers! -- Smug

Hey Smug! I just tested out my Android app with using a PDF from a URL. In this instance, it works like a charm. The PDF downloads and I can open it using a third-party app (Adobe, in this case). However, I have no such luck with local PDF files, which is important as that's how I've saved all my PDF files. I'm thinking that maybe it's not being included in the package like you mentioned, but I don't see how that can be. Everything seems to be linked up in the project. When I right click the .apk file, it comes out to 23 MB, so that part seems reasonable. Any ideas? Sorry for directing this question directly towards you, Smug, just in a "desperate" state trying to finally launch my first Android application :P Thanks! -Nicholas