# SharePoint Mobile Access Fails with “Something went wrong” (\`\[object Object\]\`)

**URL:** <https://community.origamiconnect.com/t/sharepoint-mobile-access-fails-with-something-went-wrong-object-object/1169>\
**Category:** Admin Tips and Shortcuts\
**Created:** [January 31, 2026, 2:08am UTC](https://community.origamiconnect.com/t/sharepoint-mobile-access-fails-with-something-went-wrong-object-object/1169 "2026-01-31T02:08:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![origami](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.origamiconnect.com/origami/32/436_2.png) [@origami](https://community.origamiconnect.com/u/origami)\
**Post date:** [January 31, 2026, 2:08am UTC](https://community.origamiconnect.com/t/sharepoint-mobile-access-fails-with-something-went-wrong-object-object/1169/1 "2026-01-31T02:08:28Z")

</div>

### Applies to

- SharePoint Online
- Custom SharePoint applications / SPFx solutions
- Mobile browsers or in-app web views (iOS / Android)

* * *

### Symptoms

When accessing a SharePoint site from a **mobile device** using a **custom application or mobile browser** , users may see:

> **Something went wrong**  
> Technical Details: `ERROR: [object Object]`

The same site typically loads correctly:

- On desktop browsers
- For Global Admins or privileged users

* * *

### Root Cause

This issue is **most commonly caused by Azure AD / Entra ID Conditional Access policies** that restrict mobile or browser-based access to SharePoint Online.

Because the error occurs **after authentication** , SharePoint may surface a generic message instead of a sign-in prompt.

* * *

### Common Conditional Access Triggers

One or more of the following policies may apply:

- **Blocked Mobile & Desktop Clients**
- **Device compliance required**
- **Approved client app enforcement (Intune)**
- **Restrictions on unmanaged or browser-based devices**
- **Blocked embedded or webview authentication**

These policies frequently affect:

- Mobile browsers (Safari / Chrome)
- Custom SharePoint applications
- Embedded web views inside mobile apps

* * *

### How to Confirm

1. Go to **Azure AD / Entra ID → Sign-in logs**
2. Filter by:

- **User**
- **Application: SharePoint Online**

1. Review failed sign-ins and check:

- Conditional Access status
- Policy name applied

If a Conditional Access policy shows **Failure** , it is the cause.

* * *

### Recommended Remediation

Depending on the organization’s security posture, administrators may:

- Allow **Browser** client access for SharePoint Online
- Exclude **SharePoint Online** from specific Conditional Access rules
- Exclude affected users or security groups
- Adjust device compliance requirements for browser access

* * *

### Microsoft Documentation

- Conditional Access client app conditions  
[How to Use Conditions in Conditional Access Policies - Microsoft Entra ID | Microsoft Learn](https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-conditional-access-conditions#client-apps)
- Control access from unmanaged devices  
[Control access from unmanaged devices - SharePoint in Microsoft 365 | Microsoft Learn](https://learn.microsoft.com/en-us/sharepoint/control-access-from-unmanaged-devices)
- Troubleshoot Conditional Access sign-in failures  
[Sign-in logs in Microsoft Entra ID - Microsoft Entra ID | Microsoft Learn](https://learn.microsoft.com/en-us/entra/identity/monitoring-health/concept-sign-ins)