'licence is expired' error if background data is off

[SantaClaus]

Hi all,

I bought the Pro version of MailDroid. I like the app a lot, but the
only problem I noticed is that, if I keep background data off, every
now and then I get the error message: "licence is expired or can't be
found" and the only way to fix it is to turn background data back on.
The point is, I don't really get an error message pop up, but I only
notice it if I open the app. This means I have no way of knowing how
long ago the app stopped working because of this, unless I keep
opening the app every 5 minutes, which defies the whole point of
having push email in the first place... I'd rather not keep background
data on because it's a big drain on the battery.

Is there any way around this, I mean, any way to make the app work
while keeping background data always off?

Thanks!

[Андрей Ловецкий]

Hi,
What do you mean by "background data"?
If you switch off any data exchange (gprs, wifi), Maildroid obviously will not be able to connect to the mail server. But you don't mean that, do you? :)

--
Sent from my Android 2.3.3 Samsung i9000 GalaxyS device by Maildroid 2.31, EWS to Exchange 2007 sp3

[Mickey Davis]

I have had something like this happen too. I don't know what you mean
by background data but it has happened to me when I was out of
internet range, in airplane mode or something similar and I get the
license notice. That's the worst time to get it because having no data
connection you can't get out of it! And those are the times you can be
productive to review your mail. But you can't with that license
notification . Very annoying. Only with 2.31.

On Jan 21, 2:41 am, SantaClaus <myemail...@googlemail.com> wrote:
> Hi all,
>
> I bought the Pro version of MailDroid. I like the app a lot, but the
> only problem I noticed is that, if I keep background data off, every
> now and then I get the error message: "licence is expired or can't be
> found" and the only way to fix it is to turn background data back on.
> The point is, I don't really get an error message pop up, but I only

> notice it if I open the ai have hadpp. This means I have no way of knowing how

[Konrad Hinsen]

SantaClaus writes:

> Is there any way around this, I mean, any way to make the app work
> while keeping background data always off?

In my experience it does. I keep background data off, but have it
switched on by Tasker for five minutes every hour and when I activate
the display. MailDroid does pick up e-mails during those five minutes,
as I see new messages every time I activate the display even before
the network comes up at that occasion.

Konrad.

[jl]

The issue here is usually one of a few a things:

1. Do you have a strong internet connection?

2. Do you have background sync turned off? License checks need it to be turned on.

3. Did you change the gmail account you bought the app with? The license is tied to that account.

4. If you go to the market for the pro version, does it ask you to buy it again?

Finally, try 

5. Assuming you have a good internet connection and background sync turned on (those can both be related),  you might have an old cached license in the google play market. To solve this, go to the settings section on the device, applications, find the google play app. Click delete data and clear cache. Then re-open up google play, accept their agreement and then try and open MD. This will force a re-sync of the license.

On Sunday, March 3, 2013 4:23:55 PM UTC-5, Chicco wrote:

There's got to be some other reason for these 'no license' messages and MailDroid not connecting. Because I never change any background data settings, instead I reboot Android and everything works just fine. This is a tiresome error that keeps recurring out of the blue driving me up the wall when I want to send or receive urgent mails ...

[jl]

No, it won't delete anything and you will get it all back when you load the play store back up.

On Sunday, March 3, 2013 6:44:42 PM UTC-5, Chicco wrote:

Thank you for your detailed response!
Since I can rule out options 1 to 4, I guess I'll go through procedure #5, hoping I won't delete anything crucial ...