- Posts: 36
- Thank you received: 0
Microsoft Windows Phone 8.1 support ends (13 Jul 2017)
Microsoft has ended support for Windows Phone 8.1
Questions about Android development and PDF
Activate a premium licence
- petr.sklenicka
- Topic Author
- Offline
- Junior Member
-
Less
More
IP: 192.168.0.71
11 years 7 months ago - 11 years 7 months ago #6980
by petr.sklenicka
Activate a premium licence was created by petr.sklenicka
Hello, I have a premium licence and I need to register it with package name. I do not know, which package name I have to use.
I have a simple application (for example application A). This is my module in Android Studio. Next, I have the second application ( B ), which uses your library. Application A (or module A) imports module B. Modules A and B have different package name.
So, my question is: which name of package I have to use for registration? A or B?
Thanks a lot.
I have a simple application (for example application A). This is my module in Android Studio. Next, I have the second application ( B ), which uses your library. Application A (or module A) imports module B. Modules A and B have different package name.
So, my question is: which name of package I have to use for registration? A or B?
Thanks a lot.
Last edit: 11 years 7 months ago by sanyu erisa.
IP: 192.168.0.71
11 years 7 months ago #6983
by radaee
Replied by radaee on topic Activate a premium licence
i think Module B if you using startIntent
- petr.sklenicka
- Topic Author
- Offline
- Junior Member
-
Less
More
- Posts: 36
- Thank you received: 0
IP: 192.168.0.71
11 years 7 months ago #6993
by petr.sklenicka
Replied by petr.sklenicka on topic Activate a premium licence
Sorry, but I do not think so. I tried it with your package name (com.radaee.reader) and licence works if application A has this package name. And I think that it is logic.
In case, that your answer is correct, then I think that I could do this:
1. Create B application, which uses your library.
2. Register package name of B.
3. Create a lot of other applications, which will use application B.
And this is nonsense, right?
In case, that your answer is correct, then I think that I could do this:
1. Create B application, which uses your library.
2. Register package name of B.
3. Create a lot of other applications, which will use application B.
And this is nonsense, right?
Time to create page: 0.395 seconds