we are developing a new mms application that works in parallel with
the original/phone provided mms application. They work on the same
content provider.
All works fine, except, we have two different icons for them, but when
we click on icon 1 -> apk 2 starts up and the other way around. The
behaviour is inconsistent, sometimes clicking icon 1 starts up apk 1 -
which is fine, but the system does not behave consistently. Basically,
it is not predictable which apk will start on clicking either of the
icons.
On Mon, Sep 24, 2012 at 8:17 AM, katarina <kdjako...@hotmail.com> wrote:
> Dear friends,
> we are developing a new mms application that works in parallel with
> the original/phone provided mms application. They work on the same
> content provider.
> All works fine, except, we have two different icons for them, but when
> we click on icon 1 -> apk 2 starts up and the other way around. The
> behaviour is inconsistent, sometimes clicking icon 1 starts up apk 1 -
> which is fine, but the system does not behave consistently. Basically,
> it is not predictable which apk will start on clicking either of the
> icons.
> Does anybody have any idea why is this happening?
> Many thanks for any help indeed.
> Katarina
> --
> 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@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
Can it be because we have another application on the phone with the
same name - com.android.mms.MmsApp and another activity (in a
different application) with the same name
com.android.mms.ui.ConversationList?
What has to be unique on the system - application name, activity
name?
Thanks in advance for any possible hints,
Katarina
On Sep 24, 7:37 pm, Justin Anderson <magouyaw...@gmail.com> wrote:
> On Mon, Sep 24, 2012 at 8:17 AM, katarina <kdjako...@hotmail.com> wrote:
> > Dear friends,
> > we are developing a new mms application that works in parallel with
> > the original/phone provided mms application. They work on the same
> > content provider.
> > All works fine, except, we have two different icons for them, but when
> > we click on icon 1 -> apk 2 starts up and the other way around. The
> > behaviour is inconsistent, sometimes clicking icon 1 starts up apk 1 -
> > which is fine, but the system does not behave consistently. Basically,
> > it is not predictable which apk will start on clicking either of the
> > icons.
> > Does anybody have any idea why is this happening?
> > Many thanks for any help indeed.
> > Katarina
> > --
> > 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@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-developers+unsubscribe@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/android-developers?hl=en
> > On Mon, Sep 24, 2012 at 8:17 AM, katarina <kdjako...@hotmail.com> > wrote: > > > Dear friends,
> > > we are developing a new mms application that works in parallel with > > > the original/phone provided mms application. They work on the same > > > content provider. > > > All works fine, except, we have two different icons for them, but when > > > we click on icon 1 -> apk 2 starts up and the other way around. The > > > behaviour is inconsistent, sometimes clicking icon 1 starts up apk 1 - > > > which is fine, but the system does not behave consistently. Basically, > > > it is not predictable which apk will start on clicking either of the > > > icons.
> > > Does anybody have any idea why is this happening?
> > > Many thanks for any help indeed.
> > > Katarina
> > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Android Developers" group. > > > To post to this group, send email to android-d...@googlegroups.com<javascript:> > > > To unsubscribe from this group, send email to > > > android-developers+unsubscribe@googlegroups.com <javascript:> > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en
On Mon, Oct 8, 2012 at 4:19 PM, katarina <kdjakovi...@gmail.com> wrote:
> Can it be because we have another application on the phone with the
> same name
Hm, I don't think this is even possible - how do you achieve this?
IIRC if you try to "adb install" an .apk with a package name that's
installed already it will return an error and do nothing (unless you
use -r that is, but that would make it a different operation).
latimerius wrote: > katarinawrote: > > Can it be because we have another application on the phone with the > > same name
> Hm, I don't think this is even possible - how do you achieve this? > IIRC if you try to "adb install" an .apk with a package name that's > installed already it will return an error and do nothing (unless you > use -r that is, but that would make it a different operation).
Also. you aren't supposed to name applications with someone else's domain.
So unless you own android.com, you aren't supposed to name your app com.android.anything.
thanks very much for your answers, we didn't know about domains, will
have to change that.
Actually the apk file has a different name, but within the Manifest we
have application and activity names the same as the original mms
application - do you think this can produce the cofusion too?
Can it be because of the applicaiton name inside the Manifes or
activity name inside the Manifest - do they have to be unique across
all Manifest files?
Thanks again very much for your answers, we are novices with Android
and ignorant of many things.
Regards,
Katarina
On Oct 8, 8:14 pm, Lew <lewbl...@gmail.com> wrote:
> latimerius wrote:
> > katarinawrote:
> > > Can it be because we have another application on the phone with the
> > > same name
> > Hm, I don't think this is even possible - how do you achieve this?
> > IIRC if you try to "adb install" an .apk with a package name that's
> > installed already it will return an error and do nothing (unless you
> > use -r that is, but that would make it a different operation).
> Also. you aren't supposed to name applications with someone else's domain.
> So unless you own android.com, you aren't supposed to name your app
> com.android.anything.
On Tue, Oct 9, 2012 at 9:30 AM, katarina <kdjakovi...@gmail.com> wrote:
> Actually the apk file has a different name, but within the Manifest we
> have application and activity names the same as the original mms
> application - do you think this can produce the cofusion too?
> Can it be because of the applicaiton name inside the Manifes or
> activity name inside the Manifest - do they have to be unique across
> all Manifest files?
I believe the APK file name doesn't really matter much. It's what you
put into your manifest - specifically, the <manifest> element has a
"package" attribute whose value is your package name. This package
name has to be unique - I don't think Android package manager would
let you install two different APKs on the same device whose manifests
both declared the same package name.
I guess it would be useful if you post more details about what exactly
you do - at least the manifests and how you install your APKs on your
device.
I have seen this, historically, on older phones using HTC's sense ui. The application launcher would cache the invokable target using properties of the AndroidManifest. It seemed to eventually go away, specifically if the device was restarted. I noticed this specifically when we changed the name of the Application class on these devices.
On Tuesday, October 9, 2012 9:40:40 AM UTC-5, latimerius wrote:
> On Tue, Oct 9, 2012 at 9:30 AM, katarina <kdjak...@gmail.com <javascript:>> > wrote: > > Actually the apk file has a different name, but within the Manifest we > > have application and activity names the same as the original mms > > application - do you think this can produce the cofusion too?
> > Can it be because of the applicaiton name inside the Manifes or > > activity name inside the Manifest - do they have to be unique across > > all Manifest files?
> I believe the APK file name doesn't really matter much. It's what you > put into your manifest - specifically, the <manifest> element has a > "package" attribute whose value is your package name. This package > name has to be unique - I don't think Android package manager would > let you install two different APKs on the same device whose manifests > both declared the same package name.
> I guess it would be useful if you post more details about what exactly > you do - at least the manifests and how you install your APKs on your > device.
The package name is unique accross the system, but the application
name and the activity name are the same as names of a different (stock
mms) application.
As I understood from the link RichardC posted, the name of a component
is a unique identifier as a combination of the Manifest package name,
so in our case even though activity and application name have their
clones in other packages, they should be unique as identifiers. But
could this again produce the confusion when launchig up? Or it is the
cashing issue as Nicolas mentioned?
Thanks a lot to everybody!
On 9 окт, 20:53, RichardC <richard.crit...@googlemail.com> wrote:
just to let you know that the problem was that we've put the
taskAffinity="android.task.mms" for the application to be the same as
for the original mms application, and then they were considered to be
same tasks and the activities were randomly called by the launcher.
Makes sense, and thanks for all yor advice, we'll have to put
apropriate names to our items.
All the best,
Katarina
On 10 окт, 09:15, katarina <kdjakovi...@gmail.com> wrote:
> The package name is unique accross the system, but the application
> name and the activity name are the same as names of a different (stock
> mms) application.
> As I understood from the link RichardC posted, the name of a component
> is a unique identifier as a combination of the Manifest package name,
> so in our case even though activity and application name have their
> clones in other packages, they should be unique as identifiers. But
> could this again produce the confusion when launchig up? Or it is the
> cashing issue as Nicolas mentioned?
> Thanks a lot to everybody!
> On 9 окт, 20:53, RichardC <richard.crit...@googlemail.com> wrote:
