CoreTelephony is not available when building for watchOS Simulator.

[yura2000]

Hello! I need to add Apple Watch extension for my already existing application. Successfully have added the watch app through the XCode (pic 1). Then when I'm trying to run the app trought the XCode (because running in Flutter not working (pic 2)) on an iPhone or Emulator, I'm getting an error 'CoreTelephony is not available when building for watchOS Simulator.' (pic 3)

pubspec.yaml

environment: sdk: ">=2.12.0 <3.0.0"

dependencies:
app_settings: ^4.1.1
audioplayers: ^0.20.1
auto_route: ^3.2.0
cached_network_image: ^3.2.0
carousel_slider: ^4.0.0
connectivity_plus: ^1.0.4
cupertino_icons: ^1.0.4
dartx: ^1.0.0
dio: ^4.0.4
equatable: ^2.0.3
firebase_core: ^1.10.5
firebase_crashlytics: ^2.4.3
firebase_messaging: ^10.0.4
fl_chart: ^0.35.0
flutter:
sdk: flutter
flutter_bloc: ^7.0.0
flutter_keyboard_visibility: ^5.0.2
flutter_local_notifications: ^8.0.0
flutter_localizations:
sdk: flutter
flutter_secure_storage: ^5.0.2
flutter_spinkit: ^5.0.0
flutter_swipecards: ^0.2.1
flutter_webrtc: ^0.8.0
fpdart: ^0.0.12
hive_flutter: ^1.1.0
intl: ^0.17.0
local_auth: ^1.1.6
logger: ^1.1.0
pedantic: ^1.11.0
percent_indicator: ^3.3.0-nullsafety.1
pretty_dio_logger: ^1.1.1
provider: ^6.0.1
retrofit: ^3.0.0
rxdart: ^0.27.3
sdp_transform: ^0.3.2
shared_preferences: ^2.0.11
shimmer: ^2.0.0
sliding_sheet: ^0.5.0
table_calendar: ^3.0.1
url_launcher: ^6.0.15
video_player: ^2.2.0
wakelock: ^0.5.6
web_socket_channel: ^2.1.0
webview_flutter: ^2.6.0

dev_dependencies:
auto_route_generator: ^3.2.0
build_runner: ^2.1.5
flutter_test:
sdk: flutter
freezed: ^1.1.0
hive_generator:
git:
url: git://github.com/yura2000/hive.git
path: hive_generator
json_serializable: ^6.1.1
retrofit_generator: ^3.0.0+2

dev_dependency_overrides:
analyzer: 1.4.0

flutter:
uses-material-design: true

Logs

[✓] Flutter (Channel stable, 2.8.1, on macOS 11.6 20G165 darwin-x64, locale en-GB)
• Flutter version 2.8.1 at /Users/Admin/fvm/versions/stable
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 77d935a (4 weeks ago), 2021-12-16 08:37:33 -0800
• Engine revision 890a5fca2e
• Dart version 2.15.1

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/Admin/Library/Android/sdk
• Platform android-31, build-tools 30.0.3
• Java binary at: /Applications/Android Studio 4.2 Preview.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 13.0)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.11.2

[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
• Android Studio at /Applications/Android Studio 4.2 Preview.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] VS Code (version 1.63.2)
• VS Code at /Users/Admin/Desktop/Visual Studio Code.app/Contents
• Flutter extension version 3.32.0

[✓] Connected device (3 available)
• Apple Watch Series 7 - 45mm (mobile) • 7DD6C982-C397-49EF-9ABB-69ABC5349A8D • ios • com.apple.CoreSimulator.SimRuntime.watchOS-8-0 (unsupported) (simulator)
• iPhone 13 (mobile) • 5FFE3A98-0C15-4029-91F4-60C2E7AC3318 • ios • com.apple.CoreSimulator.SimRuntime.iOS-15-0 (simulator)
• Chrome (web) • chrome • web-javascript • Google Chrome 97.0.4692.71
! Error: iPhone is not connected. Xcode will continue when iPhone is connected. (code -13)

! Doctor found issues in 1 category.

[darshankawar]

@yura2000
Flutter doesn't yet fully support watchOS. There's an open issue you can refer for further updates.
Closing this as a duplicate.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.