---
title: "What to check if User can not log in to  FieldBuddy Swift?"
canonical: "https://help.fieldbuddy.com/space/FBDOCS/4585160714/What%20to%20check%20if%20User%20can%20not%20log%20in%20to%20%20FieldBuddy%20Swift%3F"
format: markdown
---
Below is the guide of list of actions to perform if user can not login to FieldBuddy Swift application.

  
There are usually few different observations

- User can not enter credentials – FieldBuddy does not open OR no popup for credentials (step 1)
- User can enter credentials, but those are incorrect, or shows that user is disabled (step 2)
- User can enter credentials, popup with Swift log in is shown, and an error message is shown afterwards (step 3-6)

### Is latest FieldBuddy Swift version installed?

Check if the latest version of a FieldBuddy Swift app is installed

1. For upgrades from AppStore / Play Market – check in in the appropriate app on the phone/tablet (or better enable auto-updates)
2. For over-the-air upgrades – close (swipe up) an app and re-open it
3. Latest actual version can be found here - [https://help.fieldbuddy.com/page/fbswift](https://help.fieldbuddy.com/page/fbswift)

### Is salesforce user credentials accurate, and user is active?

Please ensure that  Salesforce user is **active** and enabled and not frozen.

1. If user is Frozen – that should be unlocked via administartor - [https://help.salesforce.com/s/articleView?id=sf.users_freeze.htm&type=5](https://help.salesforce.com/s/articleView?id=sf.users_freeze.htm&type=5)
2. there could be an that user is temporary locked due to incorrect password / wrong domain (sandbox/production/custom domain)

### Is FieldBuddy Configuration assigned and Present?

Check that user as a [Configuration](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/3107914298) Assigned

1. Open [Configuration Editor](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/4948852835) and ensure that expected user has a configuration assiged
2. And configuration is valid (via standard Validate button, that might complain about Labels or `FIELDBUDDY__sub_location__c`, those are non-critical errors)

### Is there a FieldBuddy license assigned?

  
Check if user has License assigned (*FieldBuddy license*) in setup. This is not needed in sandbox.  
If not, following screen might be shown:  


![image-20260120-083134.png](media://c053863d-725d-4a59-82ac-c9ebfc29d649)

  
Go to **Setup > Packaging > Installed Packages** and click **Manage Licenses** for the FieldBuddy managed Package

### Ensure profile access to sync class (if implementation deviates from standard profiles)

Check if user’s profile has an access to **FIELDBUDDY.cls_RemoteService** class - that is required

### Check for Mobile Sync Logs if there are any failed ones

Go to [https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5539692561/FieldBuddy+Swift+Settings+in+Configuration+Panel#Sync-Overview](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5539692561/FieldBuddy+Swift+Settings+in+Configuration+Panel#Sync-Overview)  and check if there are any failed sync logs and respective errors

---

Any chance that someone created a apex class called `Test`?