Hi there! I see you’re encountering a “forbidden” pop-up right after logging into the FSAFEDS app on your iPhone running iOS 16.7.14. Just to clarify, does this happen immediately after you enter your credentials, or does it pop up after a few moments? Also, does it show any error code like “403 Forbidden,” or just the word “forbidden”?

In the meantime, here are some straightforward steps we can try to address this issue:

1. Check your internet connection: Sometimes network restrictions or unstable Wi-Fi can cause access permission errors. Try switching between Wi-Fi and cellular data.

2. Force-close and restart the app: Swipe up from the bottom (or double-click the Home button, if your iPhone has one) to open the app switcher, then swipe the FSAFEDS app off the screen. Re-open it and try logging in again.

3. Update the app: Open the App Store, tap your profile icon, and see if there’s an update available for FSAFEDS. Running the latest version helps prevent permission issues.

4. Clear app data/cache settings: iOS apps do not have a direct cache clearing button, but reinstalling the app accomplishes this. Try uninstalling the FSAFEDS app and downloading it again.

5. Check date & time settings: Go to Settings > General > Date & Time and make sure “Set Automatically” is enabled. Incorrect time settings can cause server authentication errors.

If you’ve already tried these or the issue persists, it might be related to your account permissions or a backend server problem. Sometimes a 403 Forbidden error means the server is denying access due to authorization settings.

For that, I would recommend:

- Confirming your login credentials with your HR or benefits administrator to ensure your account has active access.
- Checking if the FSAFEDS service is undergoing maintenance or experiencing outages. I can assist in verifying that.

Could you please let me know which of the above you have tried? Also, did this issue start suddenly after a specific update or change on your device? That will help me guide you better.

I deleted app and reinstalled it. Error message pop up “forbidden” still pops up. Time and date updated automatically.

Thanks for letting me know you’ve reinstalled the app and confirmed your time and date are correct. Since the “forbidden” error still appears right after login, it’s likely related to account permissions or server-side access rather than something on your device.

Here’s what I recommend next:

1. Check Your Account Status: Sometimes, a “forbidden” error (often a 403 status) means your account doesn’t have permission to access the app services. If possible, contact your HR or benefits administrator to confirm your FSAFEDS account is active and properly set up.

2. Try Logging in on Another Platform: If you have access, try logging into your FSAFEDS account on their website via Safari on your iPhone or on a computer. Does the same “forbidden” message appear there? This can help identify whether it’s an app-specific problem or a broader account or service issue.

3. Check for Service Notices: Occasionally, FSAFEDS servers may undergo maintenance or experience temporary restrictions affecting login permissions. If you want, I can assist in verifying any current service alerts.

Given your steps so far, this issue seems to be outside the app itself and more on the account or server side. Please let me know if you can try the web login, or if you want me to help check for any ongoing system issues.

Are you comfortable sharing whether the web login shows a similar error? That’ll help pinpoint the cause.

Website Log in with no issues

Thanks for sharing that you can log in successfully on the FSAFEDS website, but the app still shows the "forbidden" error. That’s a helpful clue indicating the issue is likely app-specific rather than with your account credentials or Login.gov authentication itself.

From the search results, I found that FSAFEDS recently rebuilt their mobile app to improve security and required Apple users to delete the old app before reinstalling it. Since you've already reinstalled the app, that part is good. However, there may be a lingering issue with app permissions or token authorization between the app and Login.gov, which handles the login process.

A few next steps to try:

1. Ensure you are using the most recent version of the app: Double-check in the App Store if any new updates are available beyond your reinstall. Sometimes updates come in phases.

2. Sign out of Login.gov completely on your iPhone’s Safari or any browsers, then restart the FSAFEDS app and log in fresh. This forces all tokens and sessions to refresh.

3. Reset app permissions: Go to Settings > FSAFEDS on your iPhone, and make sure the app has necessary permissions enabled, especially for network access.

4. If none of this works, this may be a known issue related to Login.gov integration for the app. The best way forward would be to open a help ticket with the Login.gov support team, as their systems manage the authentication flow for FSAFEDS1.

Additionally, the FSAFEDS support center is available Monday through Friday from 9 am to 9 pm Eastern Time if you want to escalate directly through them as well10.

Let me know if you want help with any of these steps or opening a ticket with Login.gov. Are you satisfied with this approach so far?

Submit help desk ticket

Got it! To submit a help desk ticket for the FSAFEDS app issue, here’s how you can do it:

1. Contact FSAFEDS Benefits Counselors by phone:
- Call toll-free at 877-FSAFEDS (877-372-3337)
- TTY line: 866-353-8058
- Available Monday through Friday, 9 am to 9 pm Eastern Time

2. Send a secure message through your online FSAFEDS account:
- Log in on the FSAFEDS website and use the secure messaging feature to describe your issue.

3. If the problem might be related to Login.gov authentication (which sometimes causes “forbidden” errors):
- You can submit a help ticket directly to Login.gov support here: Login.gov Contact and Support

Unfortunately, there is no direct “submit ticket” button visible for the FSAFEDS app issues on their site, but the phone and secure messaging options are the best routes to reach support quickly1 5 6.

Would you like me to guide you step-by-step on calling or logging in to send a secure message? Or perhaps help you draft a message to send to them?