Skip to content

SquirrelPad 0.1.3 — ROM import fixes

Choose a tag to compare

@chrissotraidis chrissotraidis released this 30 Oct 01:10
· 23 commits to main since this release
91b6a07

SquirrelPad 0.1.3 improves ROM import for iPhone and iPad. This publishes the import changes already merged in #8; rebuilding with PadMint now includes them.

Changes

  • The ROM picker accepts filesystem items and validates their actual contents, so selection no longer depends on a storage provider assigning the expected file type.
  • Downloading/reading, hashing and copying the ROM happen off the UI thread. An Importing message shows progress, and duplicate import/play actions are disabled while it works.
  • App version/build metadata now comes from one release manifest, and packaging rejects mismatches.
  • Unsupported files report an error without replacing your existing ROM or saves. The supported US ROM and game code are unchanged.

Update

Build SquirrelPad again with PadMint and your own supported US ROM. Install over your current copy with the same signing account; do not delete the app to update it. No PadMint update is required to select this game release.

This release contains only SquirrelPad-v0.1.3-padmint.json and SHA256SUMS. No ROM or prebuilt IPA is published.

Verification and limits

A clean player build passed using current PadMint main, Apple Python 3.9.6 and an empty PadMint folder in 573 seconds. The required second check fetched the published 0.1.3 release into another empty PadMint folder and passed in 255 seconds. Both actual ARM64 iOS packages confirm 0.1.3/build 4 and pass their package audits. All ten regression tests passed. Anonymous recipe/checksum downloads also match the gated release assets.

The import tests cover invalid files, successful private-ROM import under an arbitrary extension, reimport, and preservation of existing data. Previous iPhone and iPad Simulator checks exercised local import and the actual Swift UI; they do not establish gameplay acceptance.

#3 stays open. The reporter's exact iOS 27.2 RC/provider failure has not been reproduced or confirmed fixed on their device. The cutscene crash reported in #2 is separate and remains outside this update. See release readiness.