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.smart_fm.list";
I just updated the types in my manifest to vnd.smart_fm_r1.list and
it's all good!
Yay. Now to release to the market!!
On Sep 15, 3:16 pm, tansaku <[email protected]> wrote:
> 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.setClassName(context,ListsList.class.getName());
> context.startActivity(intent);
>
> I just changed the app I could submit to the marketplace to
> consistently use the latter approach and it doesn't generate any of
> these resolution conflicts on the phone, so I could go ahead and
> submit it, however, the ADC app is still stuck using the old code, and
> that still generates conflicts, even though the new app is updated.
>
> To fix that I've tried removing the provider from the manifest, and
> even removing all URI content provider related code from the new app
> that I'd like to submit to the marketplace, and still the old ADC app
> is generating conflicts.
>
> What I really don't understand is how the conflicts can still be
> generated when the URI that I am using for the ADC app is
> content://fm.smart.provider.SmartFm/listslist" and the code package
> for the new app is fm.smart.r1
>
> I guess I really don't understand how the content URIs are working.
> If I can just figure out how the app is actually registering
> activities so they can be hit by URIs perhaps I can create a
> marketplace app that won't conflict with my ADC one ...
>
> On Sep 4, 3:41 am, dadical <[email protected]> wrote:
>
> > 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 market.
>
> > On Sep 4, 12:53 am,tansaku<[email protected]> wrote:
>
> > > 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)" <[email protected]>
> > > wrote:
>
> > > > 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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
