Building Timestamp Tracker iOS app and testing using only Windows PC (no Apple devices) seems very difficult, if not impossible
- EAS cloud build for iOS needs Apple dev ac; PWA support for RN and Expo apps ... etc., June 2025. Relevant extracts from it are given below with some additional current comments enclosed in [Dec. 2025: ]:
- I tried doing an EAS cloud build for iOS. But that tripped up on need for Apple developer account (which is not free)!
- [Dec. 2025: I think then I may not have tried an iOS simulator development build. I may have tried an iOS production build. "Apple Developer Program Member" seems to be the key term. That needs paid enrollment.]
- https://appetize.io/pricing -> Free plan offers 30 minutes per month with each session limited to 3 minutes. Above free plan seems to be very limited but it may be worthwhile to just try it out.
- Very tightly controlled but if one has a Mac computer then one can learn iOS app development and try it out on the simulator on it, and also on personal iOS devices (with such apps expiring in a week). ... OK that's not too bad. ... The barrier is the Mac computer. Not so friendly but one can understand it from a business and tight control point of view (with benefits of good quality and less security issues perhaps).
- [Dec. 2025: I think the above comment is about case where one is not enrolled as Apple Developer Program member.]
- React Native and Expo: Building Android APK Release using GitHub Actions; GitHub vs Google Drive for publishing APK, June 2025
- If you configure a GitHub Actions workflow to build an iOS app without any signing credentials, it will produce an unsigned .app bundle. This .app bundle is specifically designed to run on an iOS simulator, not a physical device.
- While you can technically build an unsigned .app bundle for an iOS simulator using GitHub Actions and download it, finding an online simulator service that readily accepts and runs such an unsigned .app bundle (especially within a free tier) for meaningful testing might be challenging.
- [Dec. 2025: I think the above post wrongly mentions that EAS does not provide "Simulator-Only" Output Option. Expo docs seem to mention such an option: iOS simulator development build.]
However, the key points are:
1. It is not legal under Apple’s license
Apple’s End-User License Agreement (EULA) for macOS explicitly states that macOS may only be installed on Apple-branded hardware, even in a VM. DeviceMAG+1
This applies whether:
-
macOS is running natively on hardware,
-
or inside a VM on Windows or Linux hardware.
So even if you can get it to run, doing so violates Apple’s license.
...
Me: Hmm. I have a React Native and expo app - Timestamp Tracker - discussed in earlier chats with you. It runs on Android. Theoretically it should run on iOS too.
I want to explore how I could check that out without having a Macintosh and using only free tier services.
CG ...
Option B: Expo Snack (partial, browser-based, free)
Expo Snack lets you:
-
Run React Native code in the browser
-
See iOS-style rendering
Pros:
-
Completely free
-
No Mac
-
No install
Cons:
-
Limited APIs
-
Not your full project structure
-
Not suitable for serious validation
This is more of a sanity check, not a real test.
...
Bottom line (very crisp)
-
✅ Your app should run on iOS
-
❌ You cannot test iOS properly without Apple hardware unless you use a real iPhone + Expo Go
-
❌ There is no free macOS cloud option
-
✅ Expo Go on a borrowed iPhone is the only truly free, legitimate route
Important reassurance: you do NOT need enrollment yet
Given your stated goals:
“I want to check whether my Expo / React Native app works on iOS.”
You do not need:
-
paid Apple Developer Program
-
App Store access
-
TestFlight
You only need:
-
an Apple ID (which you now have working)
-
an iPhone with Expo Go
Enrollment is a later decision, not a blocker right now.
...
BrowserStack does not automatically provide free device time; you must be accepted into the open source program. The eligibility criteria and process can vary and may include:
-
project maturity
-
community adoption
-
relevance and openness
This is typical of “free for OSS” programs.
It’s focused on testing, not building
You still need a build artifact (.ipa). BrowserStack will let you test the app, but you still need a way of building that iOS package. BrowserStack itself does not compile your iOS code — it only hosts devices for testing. That usually means:
-
generating a
.ipa(which typically requires macOS tooling like Xcode or CI that runs macOS), or -
distributing via TestFlight
So you will still face that build requirement unless you use a CI service with macOS runners.
...
Me: Will not EAS build allow me to create an .ipa file?
CG: ...
Bottom line (very crisp)
-
✅ EAS Build can generate
.ipafiles without a Mac -
❌ It does not remove Apple’s developer enrollment requirement
-
❌ It does not remove Apple’s identity/device verification
-
⚠️ Free-tier use is limited but workable for light testing
-
🔑 Apple remains the single hard gate in the entire chain
Your thinking is correct and logical — you’ve identified every possible workaround, and each one eventually runs into the same Apple-controlled choke point.
=========== end chat extracts ============
Comments
Post a Comment