In progress

Request failed: Invalid CSRF token

Error messages keep popping up every time I go to a different page of the drop down menu.  

Hi,
Which error message do you see every time? This one?: "Request failed. Reason: Invalid CSRF token. Try again or reload the app if the problem persists."

Hello! Yes, in my case too. 

Yeah i get that

yes.
After loading the game home page and choosing any item from the drop down menu.

I'm getting this error message when i change pages in the app or browser after it had been sitting for a few minutes, I also got it when trying to do setups in practice, and the lap didn't count and the driver setups were reset to the default.

It started happening after the latest new circuit was announced.

Normally able to replicate going to home from anywhere.  Second attempt then works. 

Hi guys,

Do you know what this is? it's been happening for the past 3 or 4 days.

The error message reads:

Request failed. Reason: Invalid CSRF token. Try again or reload the app if the problem persists.

This happens when clicking any menu option on the left while using Chrome 76.0.3809.100 on OSX Mojave

it's the same browser I've been using for months (except for version updates)

Since some days, it is the same at me.
I am using Win10 and newest Chrome on PC

same

This message pops up when you leave the app or the website long open in the background (round about 20 to 30 minutes) and then changing the page in-game. But if you try to change the page for the 2nd time it should work fine again.

Nevertheless we're apologise for the little inconveniences at the moment.
The developers will solve it as soon as possible.

same, happening semi-often for me

Hi Fabian and Jose, yes, they're those messages, I never close my iGP tab, and it never happened before. Now you can't even leave it open for 20 or so minutes as it gives this error message. Maybe it was a chrome update, maybe some new code related to cookies in the app, as this is what it's related to?

Regards

I posted about a similar problemem a few weeks ago, with the full error msg, but got no reply i will go bump it now

It's the same problem in the iOS app, so not just Chrome.

https://igpmanager.com/forum-thread/28074

I reported it days ago ?

Same problem here. I reloaded the app, but no change.

These issues only seem to have occured since the addition of the 2 new tracks.  1 race I got kicked out then couldn't get back in,  another race had to leave and rejoin atleast 6 times as it was so glitchy.  Come on guys, sort this out. 

Hi folks, the developers have been investigating this issue, so it will be addressed as soon as possible.

At the moment, here's some things I recommend if you're running into this issue.

It seems like if the app or a browser page is left idle too long, this error message appears.
And yet it may also happen in the middle of an active session, so the CSRF dialog appears at either of these two times.

If you keep encountering the problem during a play session, try the steps below. There are three lists, one for Android, iOS, and web browsers.

For Android:
- Reload the app. This means to end the app's background process, then to launch it again.
- Open your device's application manager and find the iGP Manager app in the list of installed apps and clear the app's cache and app data.
- If you're able to log into the app, go to your account settings and press the grey 'clear cache' button.

For iOS:
- Reload the app. This means to end the app's background process, then to launch it again.
- If you're able to log into the app, go to your account settings and press the grey 'clear cache' button.

For web browsers:
- Clear the cache in your browser.
- Open the game using a new tab.

Please keep in mind, these solutions are temporary workarounds. They may stop being effective or may not work for you, but if they work, will help provide some relief from this issue. If the problem returns, these steps may have to be used again.

If you've already tried these before my post, I'm sorry that there isn't any other workaround available yet and you will have to wait for the developers to address the issue. Thank you all for your patience!