os-simulator | Operating Systems Simulator

I was developing a chat app in practice using react-native expo, but when I suddenly executed "expo start" in the usual development flow, the error "could not connect to development server" was displayed.

If you have experienced the same error and know a solution, I would appreciate it if you could help.

Since I was linking with aws-amplify just before, I thought that the one installed due to that relationship was the cause of the error, but since the application starts normally in the browser, only the iOS simulator does not work (Android is in a situation where it downloads endlessly and does not start)

What I tried

1)Delete the cache with expo start -c

2)As the error says, npm start and then reload is repeated.

3)Delete 19000 with the kill command, thinking that it is a port problem. ・ Npm install ・ Rm -rf node_modules / && rm -rf yarn_lock / && yarn install && cd ios && pod install

Nothing worked, I cannot come up with any good idea to solve it. All solutions from the research are failed. What else could I do?

Referenced links

Could not connect to React Native development server on Android

Could not connect to the development server react native ios simulator Node

package.json↓

I have written below code which is fetching 3 documents , from that document i want to display only specific filed excluding the other field

I have a flutter app that ran fine. I run into a problem every once in a while where I cannot run the app.

Usually running flutter clean && flutter pub get && cd ios && pod install && cd .. would fix the issue. This did not work that time.

The error I get is: https://dsc.cloud/d061d0/output (was too long to put here).

My deployment target is set to 12.3 in Xcode.

The following didn't help:

• https://developer.apple.com/forums/thread/656616
• The iOS Simulator deployment targets is set to 7.0, but the range of supported deployment target version for this platform is 8.0 to 12.1
• https://github.com/firebase/firebase-ios-sdk/issues/6533
• https://github.com/CocoaPods/CocoaPods/issues/10134

Does anyone know how I can fix this?

I have an app which compiles and runs fine in older Macs with Intel processors in physical devices & iOS simulators.

The same app also compiles and runs fine from newer Apple Silicon Mac with M1 processor with physical iPhone devices, but, it refuse to be compiled for iOS simulator.

Without simulator support, debugging turn around time gets gets really long so I am trying to solve this issue. Not to mention Xcode preview feature isn't working either which is annoying.

The first error that I encountered without making any changes (but moved from Intel Mac to M1 Mac) is like below.

building for iOS Simulator, but linking in dylib built for iOS, file '/Users/andy/workspace/app/Pods/GoogleWebRTC/Frameworks/frameworks/WebRTC.framework/WebRTC' for architecture arm64

The Cocoapods library that I am using is GoogleWebRTC, and according to its doc, arm64 should be supported so I am baffled why above error is getting thrown. As I have said before, it compiles fine in real device which I believe is running on arm64.

According to the doc..

This pod contains the WebRTC iOS SDK in binary form. It is a dynamic library that contains the armv7, arm64 and x86_64 slices. Bitcode is not supported. Our currently provided API’s are Objective C only.

I searched online and it appears there appears to be 2 workarounds for this issue.

1. The first one is by adding arm64 to Excluded Architectures
2. The second option is to mark Build Active Architecture Only for Release build.

I don't exactly understand if above are necessary even when I am compiling my app on M1 Mac which is running under arm64 architecture, because the solution seems to be applicable only for for Intel Mac which does not support arm64 simulator, as for Intel Mac, simulators might have been running in x86_64, not with arm64, so solution #1 is not applicable in my case.

When I adapt the second change only, nothing really changes and the same error is thrown.

When I make both changes and tried building, I now get the following 2nd error during build. (not really 100% sure if I solved the 1st error / I might have introduced 2nd error in addition to 1st by adapting two changes)

Could not find module 'Lottie' for target 'x86_64-apple-ios-simulator'; found: arm64, arm64-apple-ios-simulator

The second library that I am using is lottie-ios and I am pulling this in with a swift package manager. I guess what is happening is that because I excluded arm64 in build setting for iOS simulator, Xcode is attempting to run my app in x86_64. However, library is not supported running in x86_64 for some reason, and is throwing an error. I don't have much insights into what dictates whether or not library can run in x86_64 or arm64 so I couldn't dig to investigate this issue.

My weak conclusion is that GoogleWebRTC cannot be compiled to run in iOS simulator with arm64 for some reason (unlike what its doc says), and lottie-ios cannot be compiled to run in iOS simulator with x86_64. So I cannot use them both in this case.

Q1. I want to know what kind of changes I can make to resolve this issue...

The app compiles and runs perfectly in both device & simulator when compiled from Intel Mac. The app compiles and runs fine in device when compiled from Apple Silicon Mac. It is just that app refuse to be compiled and run in iOS simulator from Apple Silicon Mac, and I cannot seem to figure out why.

Q2. If there is no solution available, I want to understand why this is happening in the first place.

I really wish not to buy old Intel Mac again just to make things work in simulator.

I want to have some XCFrameworks into an umbrella framework or umbrella xcframework using Xcode 12.4 for iOS. I tried all the approaches mentioned in these threads. However, I am not able to get it working for any of the swift classes in my client app.

Note that this works seamlessly with ObjC classes.

Umbrella framework

XCFramework with static frameworks sub dependencies

Approach 1 - Create .framework

When I build a .framework by adding sub xcframeworks to copy framework build phase, I see that xcframework subprojects are extracted to static libraries ".a" files. I import this .framework in my application which is ObjC + Swift, I get "No such modules" error for all the subprojects in all the swift classes which imports the umbrella framework

Approach 2 - Create .xcframework

When I create a .xcframework with all xcframework sub projects, I get No such module 'XXXX' error in x86_64-apple-ios-simulator.swiftinterface when I use the umbrella framework in the client app

Note that I am linking and embedding the umbrella / xcframework in client app.

Another Thought

Also, when I create a sample app with Xcode 12.4 and import the same umbrella framework/.xcframework, everything works fine. Is this something to do with the client app .xcodeproj created in older versions of XCode ?

I'm using the Firebase and the SDWebImageSwiftUI module in my SwiftUI 2 app with Xcode 12.3 and Cocoapod 1.10.0 on my Apple M1 MacBook Pro.

As long as I don't integrate the Firebase Analytics module via Cocoapod the app works fine but when I integrate it, I get the same error as the guy here: Xcode 12, building for iOS Simulator, but linking in object file built for iOS, for architecture arm64. His solution also works for me (exclude arm64 architecture for the project and pods).

However now the SDWebImageSwiftUI module (included via swift package manager) is complaining "Could not find module 'SDWebImageSwiftUI' for target 'x86_64-apple-ios-simulator'; found: arm64, arm64-apple-ios-simulator". If I include the module via Cocoapod then the compiler says "No such module "SDWebImageSwiftUI".

Does anyone of you has an idea on what I could do?

Any help is much appreciated

for the last few days, I was trying to figure out how to fix the issues I was having with Amplify for Flutter: error: compiling for iOS 9.0, but module 'Starscream' has a minimum deployment target of iOS 11.0 and Target of URI doesn't exist: 'package:amplify_core/amplify_core.dart'

Things I tried:

1. Following the tutorial of the doc https://docs.amplify.aws/start/getting-started/setup/q/integration/flutter. That resulted in: project directory/ios/Pods/AppSyncRealTimeClient/AppSyncRealTimeClient/Connection/AppSyncConnection/AppSyncSubscriptionConnection+ErrorHandler.swift:9:8: error: compiling for iOS 9.0, but module 'Starscream' has a minimum deployment target of iOS 11.0: project directory/build/ios/Debug-iphonesimulator/Starscream/Starscream.framework/Modules/Starscream.swiftmodule/x86_64-apple-ios-simulator.swiftmodule and Command CompileSwift failed with a nonzero exit code note: Using new build system note: Building targets in parallel note: Planning build note: Contructing build description. I uncommented the line platform :ios, '9.0' on Podfile and changed it to platform :ios, '11.0', while also changing the development target to 11 on the projects xcworkspace. The same error happened.

2. Following the tutorial of the doc https://aws.amazon.com/getting-started/hands-on/build-flutter-app-amplify/. That resulted in:Target of URI doesn't exist: 'package:amplify_core/amplify_core.dart' when I tried to import the core. Like that, I couldn't use the Amplify() class.

3. Restarting the computer.

4. Deleting the Amplify folder.

5. Running amplify uninstall, and trying from the start again.

6. Searching other posts on this and other websites.

7. Running amplify clean.

Things to note:

1. The Amplify installation, init, and configure steps returned no errors.
2. If I delete the Amplify dependencies amplify_flutter: '<1.0.0' amplify_auth_cognito: '<1.0.0' amplify_analytics_pinpoint: '<1.0.0' the app runs on the simulator just fine. As soon as I put them back the errors return.

Trying to install and utilize the https://developer.sonos.com/tools/developer-tools/sonos-simulator/

When following the install instructions and trying to install the node package via the npm install command within the directory it fails with a 404 error trying to find node-ssdp as seen from the snippet below:

When using the package amplify_api 0.1.0, if the deployment target is anything other than 9.0, iOS app will not build. Removing the API dependency or using ios: 9.0 in the podfile results in a successful build. Anyone know what's wrong or how to fix it?

Here's the output, which includes lots of errors, many of which seem repetitive.