Forum Widgets
Pack luck variation
From what I know and what I read Pack luck is based on an algorithm,but why does that algorithm favor certain people who sometimes don't even put effort in playing the game Personally I've been playing the game for 2 years,and I have never packed a highest rated players in the store
FC Mobile 26 – Not compatible on Lenovo Tab M11
Hi, I can’t install EA SPORTS FC Mobile 26 on my Lenovo Tab M11 (model TB330FU, Android 14/15). Google Play says: “This app is not compatible with your device.” The tablet meets the minimum requirements (4GB RAM, Octa-core CPU, Mali-G52 GPU with OpenGL ES 3.2 / Vulkan). My older Redmi Note 9 Pro installs and runs FC Mobile 26 without any issues. It seems the problem is with the Play Store compatibility flags rather than the hardware. Can you please check and update the manifest so that Lenovo Tab M11 users can install the game? Thanks.
Request for Clarification – Account Ban [0x00102710]
Dear EA Support Team, I am receiving a “Banned Account [0x00102710]” error message when attempting to log in to my FC Mobile account. However, I have not received any email or official notification explaining the reason for this action. I would kindly like to request information regarding the reason for the ban, and whether it is temporary or permanent. Additionally, if possible, I respectfully request a re-evaluation of the situation. I would appreciate it if you could review my account and inform me accordingly. Best regards,Critical Bug Report: Cross-Mode Default Lineup Contamination
# Executive Summary A critical system-level defect in the default lineup architecture is causing unintended lineup propagation across game modes, directly compromising competitive integrity in Tournament play. The issue has persisted for 6-7 months post-revamp without resolution. # Technical Problem Description ## Core Defect The default lineup system lacks proper mode isolation. The current implementation treats default lineups as a globally shared state rather than mode-specific configurations. Any lineup modification in one game mode triggers a system-wide override that replaces all default lineups across every game mode. ## Replication Path 1. Player establishes “Default Tournament Lineup” (e.g., 120 OVR optimal squad) 1. Player enters VSA/Division Rivals/Event mode and modifies lineup for mode-specific requirements 1. System automatically propagates this new lineup as the default across all modes, including Tournament 1. Player’s Tournament default is silently overwritten without notification or confirmation # Impact Analysis ## 1. Event-Driven Forced Modifications Event objectives (e.g., Footyverse “Score 2 goals with Van Basten”) mandate inclusion of specific player versions that may be: - Lower-rated variants of existing players - Positionally suboptimal - Chemistry-disrupting These requirements force temporary OVR reductions of 5-15 points during event completion phases. ## 2. Unintended Tournament Squad Degradation When players complete event tasks: - Their event-optimized lineup (featuring lower-rated required players) automatically becomes their Tournament default - No in-game warning indicates this replacement has occurred - Players unknowingly enter high-stakes Tournament matches with weakened squads ## 3. Competitive Disadvantage at Scale League-level consequences: - Multiple league members simultaneously affected during event windows - Opponents face 100-110 OVR squads instead of expected 115-120 OVR competition - Tournament outcomes skewed by lineup degradation rather than tactical skill - League rankings artificially depressed due to preventable losses Metrics of Impact: - Estimated 30-40% of active players affected during each event cycle - Tournament win rate reduction of approximately 15-25% during event periods - League performance gaps widening due to systemic rather than skill-based factors # Root Cause Assessment ## Architectural Flaw The system appears to implement a singleton pattern for default lineups rather than a composite pattern with mode-specific instances. # Expected System Behaviour ## Mode Isolation Requirements Independent State Management: Each game mode must maintain its own default lineup instance with zero cross-contamination 1. Explicit Modification Protocol: Tournament defaults should only change through: - Direct manual update within Tournament interface - Explicit user confirmation when attempting cross-mode updates 1. State Persistence Validation: System should verify mode-specific defaults remain unchanged after operations in other modes 1. User Notification System: Any automatic lineup change should trigger an in-game alert with rollback option ## User Interface Requirements - Clear visual indicators showing which default lineup is active per mode - Confirmation dialog when saving a lineup as default: “Apply this lineup as default for [Tournament] only or [All Modes]?” - Mode-specific default lineup management screen showing all saved defaults simultaneously # Business Impact & Priority Justification ## Why This Qualifies as Critical Priority ### 1. Competitive Integrity Violation - Tournaments often feature reward tiers (coins, player packs, rank points) - Bug-induced losses directly impact player progression and retention - Players are punished for engaging with event content—creating negative incentive structures ### 2. User Trust Erosion 6-7 month persistence suggests either: - Development team unaware of severity - Issue deprioritized despite player reports - Continued non-resolution damages player confidence in game systems ### 3. Revenue Impact Potential - Players invest resources (time/money) building competitive squads - System bug negates this investment, potentially reducing future spending - Competitive players may migrate to alternatives if integrity issues persist # Recommended Resolution Path ## Immediate Hotfix (Short-term) 1. Implement mode-specific default lineup storage in backend database 1. Add user confirmation dialog for any default lineup save operation 1. Introduce visual indicators showing active default per mode ## Long-term Solution 1. Redesign lineup management system with proper architectural separation 1. Implement comprehensive regression testing suite for cross-mode interactions 1. Add telemetry to monitor unintended lineup changes in production 1. Create user-facing “Lineup History” feature allowing rollback of unintended changes # Testing Requirements - Verify lineup isolation across all mode combinations (Tournament - VSA, Tournament - Events, etc.) - Validate lineup persistence after app restart - Confirm lineup state remains stable during event participation - Test edge cases: rapid mode switching, simultaneous event + tournament participation # Additional Context for Development Affected Game Modes: - Tournament (highest impact) - VSA (moderate impact) - Division Rivals (moderate impact) - Events (trigger source) Player Actions Triggering Bug: - Completing event objectives requiring specific players - Modifying lineups for chemistry experiments - Testing formations in different modes Duration Since Introduction: 6-7 months (post-game revamp), suggesting architectural rather than superficial bug # Closing Statement This defect represents a fundamental failure in system architecture that directly undermines the competitive framework the game is built upon. The persistence of this issue for 6+ months, despite player reports, suggests a disconnect between user experience priorities and development roadmap execution. Request for Transparency: - Acknowledgment of issue with estimated fix timeline - Interim workaround guidance for affected players - Commitment to priority escalation given competitive impact The bug punishes engagement with game content—a design anti-pattern that requires immediate executive attention and resource allocation.Issue with Footyverse Claw machine
So Apparently I did a claw machine 'play' in the game's Footyverse event section and then it said Err_cache , something like that and then I couldn't play it because when I showed I technically I couldn't play it , so I pressed the < button to go back thought it would give my 500 Footyverse token back , but it didn't It gave a link that it wouldn't open , the link is : https://eaassets-a.akamaihd.net/fifa/u/f/fcm23/prod//s/static/web/game/claw-machine/dist/index.html?v=1763121787 This couldn't be opened due to a error , I need my tokens back asap!
LOSE ACC
I used to have two separate EA-linked accounts in the game 117 and 119 Recently, whenever I try to log in—no matter which method I choose—it always loads the 119 OVR account. My 117 OVR account no longer appears, almost as if it was merged or overwritten. Has anyone experienced this issue before? Is there a way to restore my missing 117 OVR account or separate the accounts again? Any help would be appreciated.So many issues without address
So, what's the reason of creating a community if not to listen to the cry of customers? I wonder what this platform is set up for. Crashing, freezing and lagging still riddles my game all the time. I can't help but wonder, is this still the game i grew up enjoying to play?F.C.B
Bug: Small Black Line on Bottom-Left Corner of Pitch & Cannot Place Substitutes Hello EA team, I am experiencing two ongoing technical issues with FC Mobile: 1. Persistent Small Black Line (Graphical Bug) A small, black line appears consistently on the bottom-left corner of the pitch during matches and in the lineup screen. (I have attached a screenshot to show this.) This bug has been present for a long time. Troubleshooting attempts: I have already tried clearing the app cache/data, updating the game and my phone's operating system, and checking graphics settings (Game Booster) without success. 2. Cannot Place Players into Substitute Slots (Lineup Management Bug) I am currently unable to drag and place players from the reserves list into any of the empty substitute slots on my main lineup screen. The slots appear to be available, but the game does not register the placement of the backup player. Device Information sm-s711b/Ds Device Model: Samsung Galaxy S23Fe Operating System: Android 16 One UI Version: 8.0 Game Version: 26.1.01
Community Highlights
- EA_Pulsar2 months ago
Community Manager
- EA_Pulsar6 months ago
- EA_Lanna8 months ago
- EA_Lanna4 months ago
Featured Places
FC Mobile
Playing EA SPORTS FC™ MOBILE? Talk about your experience on our community forums.FC Mobile Game Info Hub
Official updates and announcements for EA SPORTS FC™ MOBILE.FC Mobile General Discussion
Discuss all things game related on this EA SPORTS FC™ MOBILE community forum.FC Mobile Technical Issues
Trouble with EA SPORTS FC™ MOBILE? Issue with a crash, or error? Join this community to discuss troubleshooting.FC Mobile Bug Reports
Report bugs in EA SPORTS FC™ MOBILE and see what the community is saying on this forum.FC Mobile Limited Beta
Discuss all things EA SPORTS FC™ MOBILE Limited Beta related.
