How long will I be punished for not renewing my subscription?

Solar2D General Questions/Discussion
#41

Hi Brett

In the newest build the nagging happens if I start the simulator in or out of Lua Glider.

I’m using build 2013.1137 because then the nagging does NOT happen when I start the simulator from LuaGlider. But it still happens when I start it up outside LuaGlider.

I’m on a Mac, and I used to have a subscription. Nagging started when I didn’t renew and hasn’t stopped despite having to get a new mac that could run Mountain lion, and hence Corona.

I have not contacted the LuaGlider developers as the nagging happens outside of it as well.

Not sure what other details I can supply that are relevant.

#42

Hi @xyloidhead,

That’s odd and it shouldn’t be happening (as I mentioned, I tested from a Starter account and it doesn’t nag me). I assume you’re not running it from a command line or something? Have you cleared out all of your preferences for Corona (including ones that have “anscamobile” in them, plus the Application Support folders? I can also try to de-authorize your current machines, and see if that helps.

Best regards,

Brent

#43

Hi Brent

The true test would be to register as if you bought a copy, force that registration to expire and see if the starter account then nagged you. As that is my situation, had a license, it expired, nagging commenced.

I wouldn’t know where the preferences you mention are, are they on the account here, or somewhere on the Mac? Looked on the Account details here and that didn’t show me any variables.

Happy to try it if I can find them. Also happy to try deauthorising my machines as well. Though one thing at a time I imagine is best.

john

#44

Hi John,

OK, let’s try a few things and maybe we can pin this down in your case. First, we’ll try getting rid of the prefs on your local machine.

First, open up the Corona Simulator. Open up “Preferences…” from the app’s top menu, and click the “Deauthorize and Quit” button. This should take a few seconds, and the Simulator will then quit.

Also, make sure you don’t have another version of the Simulator running. If so, do the same process for that. And, quit LuaGlider if you have that running.

Next, remove the Corona preference files. In the OS X Finder, click on your home directory (main user) to where you see the typical folders like Documents, Movies, Music, etc. Since OS X 10.7, Apple decided to “hide” the Library folder to discourage people getting in there and messing things up. So, now you have to access that by selecting (from the top menu) “Go > Go to Folder…” and then type in “~/library” and click Go. This should take you to the Library folder.

Once in there, open the “Application Support” folder. Locate both the “Corona” and “Corona Simulator” folders and trash them.

Now, back out to the main Library folder again, and locate/open the “Preferences” folder. If you see any files that start with “com.anscamobile.”, please trash those. Also, look for the pair that starts with “com.coronalabs.” and trash those.

Finally, log out from your account on the Corona website, restart the computer, and then try re-loading the Simulator. Please then report back what happens, and we’ll go from there.

Thanks,

Brent

#45

No joy, after all that it behaves exactly the same.

I had to login to use the Simulator when I restarted it proving that it had deauthorised correctly; it didn’t quit as the button suggested so I wasn’t sure.

Oh I installed build 2013.1202 just in case it did work. But alas :frowning:

#46

OK, I just de-authorized two machines internally. Can you do the de-auth (via “Preferences…”) again on your side, and test what happens? Thanks.

#47

Ok, I deauthorised it here, much cleaner on this build.

Then started the simulator up again and had to re-register it; as you’d expect. And the first thing it did was remind me to renew my subscription :frowning: So no change.

#48

Can I offer a suggestion???  Do you have another email address you can use to register with?  This would rule out any ties to your old account after clearing all the preferences above.

#49

@xyloidhead,

Before you do as Rob suggests, please clear out your preferences again (as I detailed), quit Corona, and try to re-register. We have completely wiped all your system info internally, on the Corona servers, such that it doesn’t even “know you existed”. If this doesn’t work, then Rob’s suggestion will be the avenue to take.

Thanks,

Brent

#50

Hey Brett

Purging my system info, cleaning out my preferences, rebooting and then re-registering seems to have done the trick.

No nag screen when I just start up Corona, nor when I start it through LuaGlider.

Happy to mark it as solved, from my end.

Thanks for your time and effort.

Regards

#51

Glad to hear of your success John, I haven’t shared your success unfortunately. I can confirm that having followed Brent’s steps including: death&quit, delete all the bits in ~/Library, kill zero-brane(I recommend), log out of the website, restart machine. After the machine booted up, I loaded up corona, it asked me to sign in, then immediately hit me with the nagging screen and continues to do so once more. Worth noting however is that in my corona preferences window my subscription is listed as “Pro”. I’d hazard a guess therefore that the real solution to John’s problem was the purge you chaps did on your side:

“We have completely wiped all your system info internally”
 

Could you do the same for me?

Thanks
 

J

#52

Could you do the same for me as well?

#53

Could you do the same for me as well? :slight_smile:

Edit: Sry for the double post :slight_smile:

#54

It was indeed the purge that cured the problem. Like you I did all the steps and they had no effect until they were done in conjunction with the purge.

Good luck

#55

@Brent, sorry to be a pain but could you do the same for me please?  Thanks :slight_smile:

#56

Hi @Appletreeman,

I can request this be done internally, but have you done everything that I described above in regards to cleaning out preferences and such? (Note: if you’re on Windows I can provide a list of steps for that). After that, we’ll need to do a regular de-authorization and see if that solves it for you.

Basically, I’m glad to help by submitting these requests to the techs, but I don’t want to set a “precedent” in that everybody who sees the upgrade reminder begins requesting these low-level account purges… that will not prevent the reminder from showing up occasionally for Starter users. Thanks for your understanding. :slight_smile:

Brent

#57

I have done all the above, and even removed corona SDK from programs and “reinstalled” it. But nothing works, the reminder comes up everytime i start the simulator or trying to build. And if i starts the terminal one reminder pops up at start of terminal and one when i then start the simulator. Im on mac, if that wasnt clear :slight_smile:

So if you could help me out on your side that would really help me out. :) 

Thanks

#58

@Brent, you’ve replied to Appletreeman directly but haven’t acknowledged the requests from e7k_Erik and myself. Can we leave it with you or should we be trying to lodge a support request? I understand that the forums aren’t really the place for a request like this, I was just hoping I could get a sneaky quick fix.

Thanks

J

#59

Brent,

Could you please provide instructions for the windows users as that is what I am developing on and am starting to get these nagging screens popping up as well. I love corona but just can’t afford the price of a pro version.

Thanks.

#60

Hi @marcs, sabelo, Appletreeman, e7k_Erik,

Your accounts are now cleared, so if you register an existing development machine, the popup issue should be solved.

For future requests of this nature, developers should e-mail support@coronalabs.com, and only if the usual steps of requesting a de-auth do not resolve the behavior.

@betsyjsg, your request may require accessing the Windows registry, which I’m not sure if you’re comfortable doing. Please e-mail me separately (brent@) and I’ll do my best to guide you through the process.

Best regards,

Brent