Support Topics Documentation Slack YouTube Blog

Email verify links problem

EMAIL VERIFY LINKS PROBLEM:

I first noticed the problem after deleting my own user data linked to my email…
I then remade my user account (through my app as usual)…
but since then every email verify link generated has been giving an odd error message…

Backendless Version (Online)

Client SDK ( REST )

Application ID: FF55A111-06AF-7EB1-FFDE-B5B62760CA00

Expected Behavior

Please describe the expected behavior of the issue, starting from the first action.

  1. Player registers a user account
  2. Player gets email and clicks verify link
  3. Player is taken to verification page and is now verified

Actual Behavior

Please provide a description of what actually happens, working from the same starting point.

  1. Player registers
  2. Player receives verify email…
    (before the errors… links were like this)
    http://app.jesteroc.games/api/FF55A111-06AF-7EB1-FFDE-B5B62760CA00/82FDDA42-1FDF-44D7-AE6B-31BF11B112DB/users/confirmation
    (but now:) (LINK IS WAY LONGER AND LOOKS BONKERS)
    http://app.jesteroc.games/api/FF55A111-06AF-7EB1-FFDE-B5B62760CA00/eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhcHBJZCI6IkZGNTVBMTExLTA2QUYtN0VCMS1GRkRFLUI1QjYyNzYwQ0EwMCIsImV4cCI6MTYxNjEwMDI5OSwidXNlcklkIjoiNDczMjkxQzctNzlCRi00RjEzLUJBM0YtNkQyRjMyQTMzOTgxIn0.E-Ziav_QlhnR3RuMGUP-KzopvyCCzg5ItvQTfTjhf5Q/users/confirmation
    player clicks the long bonkers looking link…
  3. player goes to the link page and the following message is shown:

{“code”:8002,“message”:“Could not parse request with message: , status code 404, headers GET /FACE4E98-ACEA-661D-F09C-A2708D04A14F/FACE4E98-0011-661D-F09C-A2708D04A14F/FF55A111-06AF-7EB1-FFDE-B5B62760CA00/eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhcHBJZCI6IkZGNTVBMTExLTA2QUYtN0VCMS1GRkRFLUI1QjYyNzYwQ0EwMCIsImV4cCI6MTYxNjEyMDA0MywidXNlcklkIjoiRDBERjM5QzctNzVDMS00NTA3LUJCMzItOTA3Mzg1MTA3RjNDIn0.YOhUSpkZ_YPFAtYL3uv3ODhLKnV5IbQeJ4ZfiOZuOjE/users/confirmation”,“errorData”:{}}

Hi @JesterOC

This is a known issue. The internal ticket: BKNDLSS-24332. We apologise for the inconvenience and will try to resolve it as soon as possible.

Best Regards,
Maksym

Hi Jessie,

The problem has been fixed. Could you please check and confirm on your end as well?

Regards,
Mark

Hi there,

Yes I can confirm it has been fixed on my end.
Now it all works again.

Thanks for the quick response.
Cheers,
Jessie