Wow reading this first would have saved me a many, many hours.
It's not just WebView apps, but can be as simple as Hello,World. I
had a pretty complex app with intents in a tabhost that I thought was
the problem, whittled down to a simple tabhost app with Intents, down
to a tabhost with a view
A quick workaround for this in Eclipse, is to set your application's
Run Configuration's Launch Action to Do Nothing. Now when you press
the play icon to launch, it seems to just push the apk to the emulator
and not launch it.
Then you go in and click your app icon, and launch/relaunch behavior
Hi Mark, thank you very much for your reply.
I have some more findings to report! Turns out it's not just
launching it from Eclipse that causes this behavior, but also
downloading the apk from the Android web browser, installing it, and
tapping the launch button.
I set up a basic hello world
I did a little poking around and I think I can DEFINITELY shine some
light on this.
Basically, I think the difference lies in the way Eclipse ports the
apk to the emulator and launches it.
I just downloaded GeoWebOne from the AdvAndroid site, created an
Eclipse project out of it. No problems
j wrote:
I launch my TestWebView activity. After my web page is loaded, I put
the app in the background by pressing the Home key. Then I bring the
TestWebActivity back to the foreground. Unexpectedly, TestWebView's
onCreate() is called when I bring the activity to the foreground. But
5 matches
Mail list logo
