mirror of
https://github.com/forcedotcom/afv-library.git
synced 2026-07-31 12:08:03 +08:00
c611126c2f
* Rename webapplication skills to ui-bundle
Rename all 7 webapplication skill directories and their content to use
the "ui-bundle" / "UIBundle" naming convention, aligning with the
New++ (TDX) naming strategy.
Directory renames:
- deploying-webapplication → deploying-ui-bundle
- generating-webapplication-{features,metadata,ui} → generating-ui-bundle-*
- implementing-webapplication-{agentforce-conversation-client,file-upload} → implementing-ui-bundle-*
- using-webapplication-salesforce-data → using-ui-bundle-salesforce-data
Content updates across all skills:
- Frontmatter name fields
- Prose: "web application" → "UI bundle"
- Metadata refs: WebApplication → UIBundle, webapplications/ → uiBundles/
- CLI: sf webapp → sf ui-bundle
- NPM packages per rename table
- Cross-skill references and generating-experience-react-site refs
* Rename generating-ui-bundle-ui skill to building-ui-bundle-frontend
The "ui-bundle-ui" name was confusing. "building-ui-bundle-frontend"
better conveys that this skill handles the React frontend layer
within a UI bundle.
---------
Co-authored-by: gbockus-sf <76090802+gbockus-sf@users.noreply.github.com>
58 lines
1.5 KiB
Markdown
58 lines
1.5 KiB
Markdown
# Troubleshooting
|
|
|
|
Common issues when using the Agentforce Conversation Client.
|
|
|
|
---
|
|
|
|
### Component throws "requires agentId"
|
|
|
|
**Cause:** `agentId` was not passed.
|
|
|
|
**Solution:** Pass `agentId` directly as a flat prop:
|
|
|
|
```tsx
|
|
<AgentforceConversationClient agentId="0Xx000000000000AAA" />
|
|
```
|
|
|
|
---
|
|
|
|
### Chat widget does not appear
|
|
|
|
**Cause:** Invalid `agentId` or inactive agent.
|
|
|
|
**Solution:**
|
|
|
|
1. Confirm the id is correct (18-char Salesforce id, starts with `0Xx`).
|
|
2. Ensure the agent is Active in **Setup → Agentforce Agents**.
|
|
3. Verify the agent is deployed to the target channel.
|
|
|
|
---
|
|
|
|
### Authentication error on localhost
|
|
|
|
**Cause:** `localhost:<PORT>` is not trusted for inline frames.
|
|
|
|
**Solution:**
|
|
|
|
1. Go to **Setup → Session Settings → Trusted Domains for Inline Frames**.
|
|
2. Add `localhost:<PORT>` (example: `localhost:3000`).
|
|
|
|
**Important:**
|
|
|
|
- This setting should be **temporary for local development only**.
|
|
- **Remove `localhost:<PORT>` from trusted domains after development**.
|
|
- **Recommended:** Test the Agentforce conversation client in a deployed app instead of relying on localhost trusted domains for extended periods.
|
|
|
|
---
|
|
|
|
### Blank iframe / auth session issues
|
|
|
|
**Possible cause:** First-party Salesforce cookie restriction may block embedded auth flow in some environments.
|
|
|
|
**Solution:**
|
|
|
|
1. Go to **Setup → Session Settings**.
|
|
2. Find **Require first party use of Salesforce cookies**.
|
|
3. Disable it **only if needed and approved by your security/admin team**.
|
|
4. Save and reload.
|