Hi! I see you're encountering error code 5001 in the PLAYFUL REWARDS app when being redirected using Chrome on your iPhone. Let's get to the bottom of this together.

To start, could you share a bit more? For example:
- When exactly does the error appear? Is it right after clicking a link that opens another app, or during some specific action?
- Does this happen every time or only occasionally?
- Have you tried using any other browser or clearing Chrome’s cache?

In the meantime, here are some first steps you can take to troubleshoot this on your iPhone with iOS 18.6.2:

1. Close and Reopen Apps: Fully close both PLAYFUL REWARDS and Chrome. To do this, swipe up from the bottom of the screen and pause, then swipe each app off the screen. Then reopen them.

2. Clear Chrome Cache: Cache or stored browsing data can sometimes cause redirect errors.
- Open Chrome.
- Tap the three-dot menu at the bottom right.
- Go to Settings > Privacy > Clear Browsing Data.
- Select Cached Images and Data, then tap Clear Browsing Data.

3. Check for Updates: Ensure both the PLAYFUL REWARDS app and Chrome are updated to their latest versions via the App Store.

4. Try Incognito Mode: In Chrome, open a new Incognito tab and try the redirection again. This disables extensions and cached data.

5. Restart Your iPhone: A simple restart can fix network or temporary glitches.

If after these steps the error persists, the 5001 code might relate to an internal problem in how the PLAYFUL REWARDS app handles redirects from Chrome, possibly a "Too Many Redirects" loop or permission conflict.

In that case, could you try this?
- Use Safari instead of Chrome to access PLAYFUL REWARDS and see if the redirect works there.
- Check if you have any content blockers or VPNs active that might interfere.

If none of the above helps, I might need to escalate this to our development team for a deeper investigation since it seems linked to the redirect logic between Chrome and the PLAYFUL REWARDS app.

Let me know how these steps go or if you have more details about when the error occurs! Are you satisfied with this troubleshooting approach so far?