Okay, so I think I fixed this. The provider in my ADC was calling a
ResolverActivity as follows:
c.setNotificationUri(getContext().getContentResolver(), url);
and was setting particular types of query, e.g.:
case LISTS:
return "vnd.android.cursor.dir/vnd
Hmm, so I think I worked out the source of my conflict. I was calling
activities via URI rather than by class name. I was doing this:
context.startActivity(new Intent(Intent.ACTION_VIEW,
SmartFm.Lists.CONTENT_URI));
rather than:
Intent intent = new Intent(Intent.ACTION_VIEW);
intent.setClassN
I asked these same questions on this forum a couple of days ago. My
conclusion was that unless I'm willing to go through the pain of
testing and tweaking my marketplace version of the app so that it can
behave nicely with the ADC vertsion, I'm going to wait until ADC is
over to publish to the mar
Yeah - eclipse seemed to update that automatically. I think it
wouldn't have run if that was incorrect ...
On Sep 3, 6:25 pm, "Maps.Huge.Info (Maps API Guru)"
wrote:
> Did you change your package name in the manifest?
>
> -John Coryat
>
> "What Zip Code?"
--~--~-~--~~~--
Did you change your package name in the manifest?
-John Coryat
"What Zip Code?"
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@goog
5 matches
Mail list logo
