SWF Player - RetroBIOS

Type	standalone
Classification	Launchers
Source	https://play.google.com/store/apps/details?id=com.issess.flashplayer
Upstream	closed-source
Version	1.90 free (build 507)
Profiled	2026-08-12
Cores	swf-player, SWF Player, SWF-PLAYER
Systems	flash
Author	issess.net

Technical notes

Android package com.issess.flashplayer, closed source, published on Google Play and reached by ES-DE through its SWF-PLAYER find rule. The build read here is 1.90 free (build 507), versionCode 507, arm64-v8a and armeabi-v7a, sha256 0a56e74d0f8bfdfbd984ce1b8aa2a700203fdd051f3aece3c95fb17f45d4383b, signed v1 and v2 with the developer certificate O=issess.com, CN=issess, sha256 c3a222b4339f9dde3a770bc1d0ceb551fa96e554679cdbd2056aadd0f1b843c8. Line numbers below are those of that package: jadx output for the classes, the shipped file itself for contents.html. The paid package com.issess.flashplayerpro, the other entry of the same find rule, is built from this class tree, its activity being spelled com.issess.flashplayer.player.FlashPlayerActivity. No genuine copy of it was obtainable: apkpure and apkcombo bounce the download of a paid app, apkvision holds none, mi9 serves zero bytes and archive.org has no item for either package.

Two engines ship in the package, one activity each, both exported and both answering android.intent.action.VIEW for application/swf, application/x-shockwave-flash and video/x-flv. FlashPlayerActivity is labelled "SWF Player by Ruffle" and runs the movie in a WebView; AirPlayerActivity is labelled "SWF Player by AdobeAIR", lives in a :air process and drives a captive Adobe AIR runtime. ES-DE names the first one and passes the movie as the content URI of its own provider, so it always gets the Ruffle engine. ref: AndroidManifest.xml activity com.issess.flashplayer.player.FlashPlayerActivity and .AirPlayerActivity, string play_ruffle_player, play_air_player, using_ruffle_plugin, using_air_plugin

The movie itself never stays where the user put it. BaseActivity.E reads the intent Uri through the content resolver, or opens the path directly for a file:// intent, and writes the bytes twice: to /assetLoader/cached.swf for the WebView engine and to /app//assets/cached.swf for the AIR engine, next to a copy of the bundled AIR descriptor. The AIR name is fixed because the descriptor declares cached.swf as its initial window content. A run with no Uri falls back to the last_swf preference. ref: BaseActivity.java:607-654, BaseActivity.java:594-605 (uniqueappversionid), a2/b.java:86-92 (asset copy), a2/b.java:115 (stream copy), assets/META-INF/AIR/application.xml:28

The Ruffle engine serves everything over a virtual host. FlashPlayerActivity.g0 writes /assetLoader/swf.html from the bundled contents.html template, substituting the movie URL and the wmode, scale, quality, background and density preferences; FlashPlayerActivity.h0 builds a WebViewAssetLoader on the domain localhost.issess.net mapping /ruffle/ to the package assets and / to that cache directory; i0 then loads https://localhost.issess.net/swf.html one second later. The template pulls /ruffle/ruffle/ruffle.js, which resolves to assets/ruffle/ruffle.js, and declares the movie as a plain