improving standalone app creation

[Copilot]

Fixes the issue where FlowTimer would build and run from command line on Apple Silicon Macs but fail to start when installed in the Applications folder and launched via Spotlight.

Problem

The application was experiencing startup failures when moved to /Applications/ due to several issues in the macOS app bundle creation and launcher script:

1. Failed ARM64 library copy: create-app.sh was attempting to copy a non-existent libJNativeHook.arm64.dylib file
2. Poor working directory resolution: The launcher couldn't properly locate resources when started from Applications folder
3. Inadequate Java detection: Limited Java discovery logic that failed in various macOS configurations
4. Missing macOS app bundle configuration: Info.plist lacked required keys for proper app behavior

Root Cause Analysis

Investigation revealed that native ARM64 libraries were actually already present:

• JNativeHook 2.2.2 includes com/github/kwhat/jnativehook/lib/darwin/arm64/libJNativeHook.dylib
• LWJGL 3.3.3 includes ARM64 libraries under META-INF/macos/arm64/

The real issue was the app bundle launcher script's inability to properly resolve paths and resources when launched from the Applications folder.

Solution

Enhanced App Bundle Creation (create-app.sh)

• Removed failing library copy: Eliminated attempt to copy non-existent ARM64 library since JNativeHook embeds libraries in JAR
• Improved Info.plist: Added essential macOS app keys including LSMinimumSystemVersion, accessibility descriptions, and app category
• Better resource handling: Added fallback logic for missing icon files

Robust Launcher Script

Created a comprehensive launcher that handles Apple Silicon deployment:

# Multi-location Java detection with version validation
find_java() {
    local java_paths=(
        "$(command -v java 2>/dev/null)"
        "/usr/bin/java" 
        "/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java"
        "$(/usr/libexec/java_home -v 17 2>/dev/null)/bin/java"
    )
    # ... validation logic
}

# Apple Silicon optimizations
if [[ "$(uname -m)" == "arm64" ]]; then
    JVM_ARGS+=("-XX:+UnlockExperimentalVMOptions" "-XX:+UseZGC")
fi

Key Improvements

• Working directory resolution: Properly changes to Resources directory regardless of launch method
• Enhanced error handling: User-friendly dialogs instead of command-line errors
• Debug logging: Comprehensive logging to /tmp/flowtimer_debug.log for troubleshooting
• Architecture detection: Automatic Apple Silicon optimizations when detected

Validation & Documentation

• Added validation script: test-app-bundle.sh performs comprehensive app bundle validation
• Updated installation docs: Step-by-step instructions for macOS installation with troubleshooting guide
• Verified native library embedding: Confirmed both Intel and ARM64 libraries are correctly included

Testing

The app bundle now passes all validation tests:

• ✅ Proper bundle structure and executable permissions
• ✅ Valid Info.plist with correct bundle identifier
• ✅ JAR integrity with embedded ARM64 and Intel native libraries
• ✅ Launcher script syntax and logic validation

Installation Process

Users can now successfully install on Apple Silicon:

./build.sh gradle
./create-app.sh  
cp -r FlowTimer.app /Applications/
# Grant accessibility permissions in System Settings → Privacy & Security → Accessibility
# Launch via Spotlight search for "FlowTimer"

This resolves the issue where the app icon would appear in Applications but the application wouldn't start when launched via Spotlight.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.