Hi all, just wondering if people are successfully building Android 3.0 apps - I'm having trouble. I recently updated to 2.1.9, which brings with it a nice option to produce a BT 3.0 Android app, or the more traditional code. I had put an app together that ran nicely on IOS and before I upgraded, it worked on Android too. Somewhere along the way, something happened and the app that compiles for IOS isn't loving Android, it just seems to keep stopping. basic. So I decided today to start from scratch. I built something that only uses core plugins. I downloaded this for BT 3.0 into Eclipse and the project compiles and runs. It uses a non tabbed layout, the home page uses an HTML file in the project, which is referenced using the HTML doc plugin. When the app loads I see a screen that invites me to open the document or download document, with the icon for the plugin shown below. By pressing the buttons, the text loads in the end, but this behavior is quite odd. The same app for Android 2 just loads the page as expected. It seems simple enough, but I don't know what the problem is!

HTMLDoc plugin has different behavior now. It acts like the PDF plugin. I wrote a replacement based on Davids old BTv2.0 Android code…. It is 'not ready for prime time' meaning, you'll need to fool with it a bit to get it into your project. It doesn't have all the features of the old plugin either. I just did a quickie mod because I had an app I needed to get out the door. The usual appDelegate errors and things might pop up because I didn't really build it for release; just to solve a quick problem. You're welcome to give it a shot: https://dl.dropboxusercontent.com/u/115208762/Sw_smugwebview/Sw_smugwebview.zip Cheers! -- Smug

Thanks Smug, I'll give it a go. I wonder what the reason is for changing the way it behaves? The old way seemed pretty good to me and I imagine this could cause a problem for people with old apps that they want to upgrade. From a UI perspective, what is the up side? Alan

We talked about it here, but I haven't heard much more about it. https://www.buzztouch.com/forum/thread.php?tid=A4A8028CBD94ED3F9249414&fid=5FE1FB2355A48AD674A6CA3&sortColumn=FT.id&sortUpDown=&currentPage=1 Considering the task list David has, I'm not sure when/if that will be remedied. In the meantime, hack away at what I've done, and you'll be ok for the interim. Cheers! -- Smug

Wow! Why hasn't there been more of a hue and cry about this? That would make me run away from BuzzTouch for Android! I am so glad I don't yet have to jump onto that Android train. I will eventually though. Hope these things are sorted out by then. -- Niraj

It was a very major rewrite of the Android Core. If you find problems you think we may have missed, feel free to send me a PM or email. I didn't know about this one, and I assumed this was its usual behavior.

Hi Susan I hope that the html doc plugin behaviour reverts to how it used to work, or at least includes all those properties, as I use html pages a lot. I prefer to create pages as html files rather than use the custom html plugin, which is OK, but has its limitations. I think the idea was to be able to use the custom url plugin instead, but if you want to cache the page, or you want to an html files into the app, that approach doesn't work.

I totally agree. I just made an app with the HTML Plugin instead of the customURL. It worked great on iOS and cached on the device. But then, when I saw how it looked in Android I reverted back to the customUrl. Niraj officially sent it over today, and I added it to the priority list.

Phew!

I should have said I added it to the list of undone work that we prioritized. The highest priority right now is getting the new iOS7 out the door. So it won't be prioritized as highly as that.

Well, at least it is on a list.