I registered but cannot complete a new activation

[Stelly604]

I've registered a new profile, but didn't finish activating the 1st time.  When I login I get the choices to complete activation or go to login page.  When I click either i get the login page, but my credentials don't work on the second time.  Only the first. 

Then it repeats the cycle even though I've reset my password twice.  

[hTideGnow]

Hi @WendyHuang 

what error you got? did you try using the app?

[WendyHuang]

same thing here

[Stelly604]

Thank you very much.  It worked with the App.  

[hTideGnow]

Hi @Stelly604 

you didn't start the subscription process on the app?

i think with the error , nothing much you can do., please submit ticket with CS agent and have them to help

https://productioncommunity.publicmobile.ca/t5/notes/composepage/note-to-user-id/22437

[Stelly604]

Still doesn't work.  

I noticed the 1st login, i get the eversafe login.

But then when I try to continue activation it kicks me out and goes back to another login but i noticed its not the eversafe login: https://identity-np.cloudapps.telus.com/user/forgotpassword?locale=en&ForceAuth=true

I get an error: Please enter a valid email address registered to your account.

[maximum_gato · Accepted solution]

@Stelly604 

Are you using the app? To finish activating you must complete it using the app. Make sure you have downloaded the latest version and clear the app cache before proceeding with the activation process. Keep an eye out for where you enter your referral code for the $10 bonus referral credit as it in tiny letters and easy to miss.

Welcome to Public Mobile!

Edit:

[Stelly604]

Ok I'll try that.  Thanks.

[Stelly604]

It looks like its a glitch with the eversafe system as i get a 6 digit code but it keeps saying its wrong.

[Chalupa_Batman]

Go into your browser settings and clear the cache cookies and history. Close and restart the browser and try again. The website has been having some cache issues lately. Not sure why Public Mobile IT isn't trying to resolve this issue as it's been ongoing for some time now.