Verification codes and app approvals during connect
When Crispy signs in to LinkedIn for you, LinkedIn sometimes challenges the sign-in, exactly as it would for a login from a new device. This is a normal checkpoint, not an error, and it can show up during first connects and reconnects alike.
There are two kinds:
- A verification code, sent by SMS or email, or generated by your authenticator app.
- An in-app approval, where LinkedIn sends a notification to your LinkedIn mobile app.
Entering a code
When the form asks for verification, type the code and click Verify. If you actually approved the sign-in in the LinkedIn app, click 'I approved it in the LinkedIn app instead' and Crispy switches to waiting mode.
Approving in the app
If LinkedIn chose the in-app route, open the LinkedIn app on your phone and approve the sign-in request. Crispy polls for up to two minutes and completes automatically once LinkedIn confirms. If it times out but you did approve, refresh the page. If you were given a code instead, click 'I have a code to enter instead'.
If it keeps failing
- After a couple of failed codes, use the 'Start over' option and begin the connection fresh.
- After several failed connection attempts, the form offers a hosted login page as an alternative route. Try it; it walks through LinkedIn's own login screens.
The one rule that matters: a connection or reconnect only counts once the checkpoint clears. Approving on your phone but closing the Crispy tab halfway leaves the account unconnected.
Pro tip: keep your phone nearby when connecting. Most checkpoints clear in under thirty seconds when you can approve immediately.