Skip to content

Releases: alespina98/FUT_Forge_Releases

v2.11.2

Choose a tag to compare

@alespina98 alespina98 released this 19 Aug 16:48
89e416c

v2.11.1

Choose a tag to compare

@alespina98 alespina98 released this 19 Aug 09:02
89e416c

FUT Forge 2.11.0

Choose a tag to compare

@alespina98 alespina98 released this 11 Aug 11:01
89e416c

English

The first official FUT Forge release for macOS.

  • Separate native downloads for Apple Silicon (arm64) and Intel (x86_64); these are not Universal2 builds.
  • Requires macOS 15 or later.
  • macOS updates are currently manual.
  • These builds are ad-hoc signed and are not Apple-notarized. On first launch, macOS may require Control-click ? Open or System Settings ? Privacy & Security ? Open Anyway. Do not disable Gatekeeper.
  • The existing Windows 2.10.1 release and Windows updater remain unchanged.

Italiano

La prima release ufficiale di FUT Forge per macOS.

  • Download nativi separati per Apple Silicon (arm64) e Intel (x86_64); non sono build Universal2.
  • Richiede macOS 15 o successivo.
  • Gli aggiornamenti macOS sono attualmente manuali.
  • Queste build hanno firma ad-hoc e non sono notarizzate da Apple. Al primo avvio macOS potrebbe richiedere Control-click ? Apri oppure Impostazioni di Sistema ? Privacy e Sicurezza ? Apri comunque. Non disabilitare Gatekeeper.
  • La release Windows 2.10.1 e il relativo updater rimangono invariati.

Windows Desktop 2.11.0

  • Refreshed the in-app interface across Dashboard, Club Insights, Fodder Value and Settings.
  • Added dedicated Summer Stars rarity artwork in Club Insights.
  • Added a verified modular runtime update foundation with an embedded fallback for reliability.

FUT Forge Android 1.0.9

Choose a tag to compare

@alespina98 alespina98 released this 19 Aug 19:48
89e416c

Diagnostic release. The 1.0.8 hotfix did not resolve the real-device updater failure (confirmed genuinely packaged in the public 1.0.8 APK). This release adds a persistent checkpoint trace of the AGGIORNA ORA/UPDATE NOW flow that survives app process death, plus an on-next-launch diagnostic dialog with a COPY DIAGNOSTIC button so a tester without ADB access can report exactly where execution stops. No security/verification behavior is weakened; no app-closing calls were found anywhere in the Android source during audit.

versionCode 10.

FUT Forge Android 1.0.8

Choose a tag to compare

@alespina98 alespina98 released this 19 Aug 18:30
89e416c

Hotfix: repairs the in-app updater's install flow. Pressing UPDATE NOW in 1.0.6/1.0.7 could silently crash the app before the unknown-sources permission screen or the Android installer ever appeared, due to update state being cleared right before the download button used it. The install flow is also hardened: failures now show a visible message and are logged instead of crashing or failing silently, and returning from the unknown-sources Settings screen automatically resumes the verified install without a second button press.

versionCode 9. SHA-256 verification and same-certificate upgrade behavior are unchanged.

FUT Forge Android 1.0.7

Choose a tag to compare

@alespina98 alespina98 released this 19 Aug 18:03
89e416c

Dashboard parity update: square icon containers and compact card layout, matching Desktop 2.11.2 / Extension 2.10.5.6. Preserves the 1.0.6 EVO Builder mobile scrolling fix, official launcher icon, and all existing authentication/updater/WebView behavior.

versionCode 8.

FUT Forge Android 1.0.6

Choose a tag to compare

@alespina98 alespina98 released this 19 Aug 13:19
89e416c

FUT Forge Android 1.0.6

  • Fixed EVO Builder layout and scrolling on mobile devices
  • Eligible Evolutions and Suggested Paths are now fully accessible
  • Improved Android WebView mobile rendering
  • Added the new official FUT Forge Android launcher icon
  • General Android compatibility and UI improvements

FUT Forge Android 1.0.13

Choose a tag to compare

@alespina98 alespina98 released this 20 Aug 11:04
89e416c

Android back gesture fix: EA's own navigation controller (UTGameFlowNavigationController) exposes no public viewControllers stack and never uses the browser History API, so the previous heuristics for detecting in-page history were unreliable and back could restart the whole app instead of navigating EA's screens. Back now uses EA's own getPreviousController()/popViewController(true) - the same signal EA's native back action relies on - confirmed working across multiple EA screens on a real device: navigates back through EA's screen stack correctly, and at the true root sends the app to the background (instead of finishing the Activity) so the WebView and session survive for the next foreground, with no restart, reload, or splash. Confirmed on a real device.

Preserves the 1.0.12 adaptive safe-area handling, the Sign Up / Forgot Password click fix, and the 1.0.11 post-install-loop fix and updater diagnostics, all untouched.

versionCode 14.

FUT Forge Android 1.0.12

Choose a tag to compare

@alespina98 alespina98 released this 19 Aug 23:16
89e416c

Three real-device UX fixes: adaptive status bar / safe area handling via WindowInsets (no hardcoded padding, reacts to whatever the device actually reports), Android back gesture now navigates EA's own in-page UTNavigationController stack (matching the official app) instead of restarting the app, and Sign Up / Forgot Password are now clickable (Android-only fix for a shared touch-tap-suppression interaction; canonical futforge_core/inject.js is unchanged). Auth-link fix confirmed working in emulated testing; safe-area and back-navigation fixes are ready for real-device validation.

Preserves the 1.0.11 post-install-loop fix and updater diagnostics.

versionCode 13.

FUT Forge Android 1.0.11

Choose a tag to compare

@alespina98 alespina98 released this 19 Aug 22:06
89e416c

Fixes the post-install update loop confirmed on real device testing of 1.0.9 -> 1.0.10: after a successful in-app update, reopening FUT Forge reopened the installer again. Root cause was stale downloaded-APK state that was never cleared once the installed app already matched the version it was for. The pending state now carries its target versionCode/versionName and is cleared automatically once BuildConfig.VERSION_CODE meets or exceeds it. The diagnostic dialog's 'Target: ?' gap is fixed the same way. No changes to download logic, SHA-256 verification, FileProvider, or the install intent itself.

versionCode 12.