This issue is very annoying. This prevents applications with a
subclass of Mapview and a widget to cohesist together.
This is a major issue.
Does anybody succeed in having both?
Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
I am using the Google Api 1.5 that already has the maps.jar and
already included the uses-database in the manifest but still getting
that errror.
any ideas?
thansk
On Jun 9, 4:42 am, broc sebastien.peroc...@gmail.com wrote:
Hi,
As Zach Hobbs wrote on month ago, a solution is to launch
Hi,
As Zach Hobbs wrote on month ago, a solution is to launch either the
widget or the configure activity (and all sub-activities containing
the MapActivity) in an another process than the application by
specifying in the AndroidManifest.xml file the option
android:process as following:
For
I answer to myself: the licence agreement of the maps api doesn't
allow to include the jar in an application...
So, I have no answer...
Please release a 1.5 r3 with this bug corrected :-))
On 6 juin, 21:21, broc sebastien.peroc...@gmail.com wrote:
The only solution that works for me, but is a
This happens on the device too and is kind of a show stopper. So
there is really no workaround for this?
I guess we are to assume that having both a widget and a MapActivity
is not fully supported under 1.5, which is a shame.
-Alex
--~--~-~--~~~---~--~~
You
Hi,
Is this bug limited to the SDK (=only on the emulator) or is it
existing on real phone too ?
Thanks,
Sebastien.
On 12 mai, 02:52, Dianne Hackborn hack...@android.com wrote:
Hi, it looks like there is a bug initializing a process when it is launched
to handle a broadcast sent to an
I can run the BroadcastReceiver in another process and it does fix it,
only problem is peekService() doesn't appear to be working for me
across processes :(
Thanks anyways for the info.
-Zach
On May 11, 8:52 pm, Dianne Hackborn hack...@android.com wrote:
Hi, it looks like there is a bug
Not doing any instrumentation tests. The superclass of
MusicMapActivity is com.google.android.maps.MapActivity, so how could
this class not be found? I do have uses-library
android:name=com.google.android.maps / in my Manifest under my
application/ tag.
Thanks,
-Zach
On May 8, 4:15 pm,
I have the same problem it seems, except mine always crashes. I've
never had it work. My LogCat is almost identical to the one above
(with obvious changes). It does not seem to be able to resolve the
superclass of any class that extends MapActivity. Any help would be
greatly appreciated!
On
Some more information:
it only happens if I have a widget (unrelated to maps) enabled on the
Launcher the first time I access this MapActivity
-Zach
On May 11, 12:34 pm, Zach Hobbs ho...@helloandroid.com wrote:
Not doing any instrumentation tests. The superclass of
MusicMapActivity is
Hi, it looks like there is a bug initializing a process when it is launched
to handle a broadcast sent to an explicit component. In this case its
shared libraries are not linked to it. This will be fixed in a future
release, but I don't know of a work-around for 1.5.
On Mon, May 11, 2009 at
On May 7, 12:52 pm, Zach Hobbs ho...@helloandroid.com wrote:
05-07 15:44:32.024: WARN/dalvikvm(16630): Unable to resolve superclass
of Lcom/tunewiki/lyricplayer/android/community/maps/MusicMapActivity;
(210)
05-07 15:44:32.024: WARN/dalvikvm(16630): Link of class 'Lcom/tunewiki/
12 matches
Mail list logo
