Troubleshooting guide#811
Merged
leofelix077 merged 9 commits intolf-add-freighter-mobile-best-practices-skillfrom Apr 29, 2026
Merged
Troubleshooting guide#811leofelix077 merged 9 commits intolf-add-freighter-mobile-best-practices-skillfrom
leofelix077 merged 9 commits intolf-add-freighter-mobile-best-practices-skillfrom
Conversation
…ry issues Android Studio sometimes doesn't apply RAM changes to existing AVDs reliably; recreating the emulator is the definitive fix.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a centralized troubleshooting reference for common Freighter Mobile dev environment, build, testing, and dependency issues, and links it from the contributor/agent entry-point doc.
Changes:
- Introduce
docs/troubleshooting-guide.mdwith setup/build/test/dependency troubleshooting steps and known gotchas. - Add a “Troubleshooting” row in
AGENTS.mdto surface the new guide alongside other best-practices entry points.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| docs/troubleshooting-guide.md | New troubleshooting guide covering common local dev, CI, and dependency issues. |
| AGENTS.md | Adds a pointer to the troubleshooting guide in the “Best Practices Entry Points” table. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
CassioMG
reviewed
Apr 22, 2026
CassioMG
reviewed
Apr 22, 2026
CassioMG
reviewed
Apr 22, 2026
CassioMG
reviewed
Apr 22, 2026
CassioMG
reviewed
Apr 22, 2026
CassioMG
reviewed
Apr 24, 2026
CassioMG
reviewed
Apr 25, 2026
Contributor
CassioMG
left a comment
CassioMG
left a comment
There was a problem hiding this comment.
Review of PR #811 (Troubleshooting guide). One finding worth flagging — the rest of the guide is well-researched and accurate (verified yarn scripts, file paths, Husky version, Gemfile gems, metro.config claims, and pod-install bundle exec usage all check out).
CassioMG
approved these changes
Apr 25, 2026
Contributor
CassioMG
left a comment
CassioMG
left a comment
There was a problem hiding this comment.
Lgtm - left a couple comments
…er-mobile into lf-troubleshooting-guide
CassioMG
approved these changes
Apr 29, 2026
…ctices-skill' into lf-troubleshooting-guide
leofelix077
merged commit fa6a3a2
into
lf-add-freighter-mobile-best-practices-skill
2 checks passed
leofelix077
added a commit
that referenced
this pull request
May 5, 2026
* add v1 of freighter mobile best practices skill * adjust styling and comments from copilot reviee * Adjust code review and update agentic files best practices * Unify duplicate agent instruction files Rewrite AGENTS.md as the single AI agent entry point: - Add glossary section with domain-specific terminology - Add documentation link index (replaces llms.txt) - Remove sections that duplicate best-practices reference files (code style details, branch conventions, PR instructions) - Keep unique context: repo map, architecture orientation (ducks/nav/WC), security alert list, known complexity/gotchas, pre-submission checklist - Delete llms.txt (content absorbed into AGENTS.md) - Delete CLAUDE.md (content absorbed into AGENTS.md) * minor adjustments from copilot code review * Apply suggestion from @CassioMG * remove direct mentions of freighter deep links * update comments from performance.md claude review Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * adjust deep link and install comments from code review Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Apply suggestion from @CassioMG * cleanup cross-information with extension and hard examples Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix deeplink * add superpowers suggestions to best practices * remove mentions of push tokens * adjust comments from code review and enforce SDS components rule * clear up code examples and sds components * Troubleshooting guide (#811) * fix(troubleshooting): add emulator recreation tip for persistent memory issues Android Studio sometimes doesn't apply RAM changes to existing AVDs reliably; recreating the emulator is the definitive fix. * cleanup runtime information and clipboard not pasting * Update code review troubleshooting comments * cleanup references naming * clean up troubleshooting guide for stable xcode and IDE config * breakdown commands on troubleshooting guide for better readability * remove xcode 26 regression issue * move changes out of skill folder * adjust code snippets and last update date --------- Co-authored-by: Cássio Marcos Goulart <3228151+CassioMG@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Copilot <copilot@github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.