call to unavailable function 'fork': not available on tvOS

[lesnitsky]

I'm trying to build Flutter.framework for tvOS and getting this error. Is there a way to workaround this issue?

[lesnitsky]

https://github.com/dart-lang/sdk/blob/master/runtime/bin/process_macos.cc#L164

[devoncarew]

I'm not sure that tvOS is a supported iOS target for Flutter; will move this issue to the flutter repo.

[ghost]

This issue was moved by devoncarew to flutter/flutter#47928.

[jmagman]

I don't think this should have been moved.

HOST_OS_IOS is 1 if TARGET_OS_IPHONE, so watchOS, tvOS, Catalyst, etc. But it looks like HOST_OS_IOS is synonymous in dart-lang with iOS-only.

           TARGET_OS_IPHONE          - Generated code for firmware, devices, or simulator
              TARGET_OS_IOS             - Generated code will run under iOS 
              TARGET_OS_TV              - Generated code will run under Apple TV OS
              TARGET_OS_WATCH           - Generated code will run under Apple Watch OS
              TARGET_OS_BRIDGE          - Generated code will run under Bridge devices
              TARGET_OS_MACCATALYST     - Generated code will run under macOS

I believe @lesnitsky is asking for "sdk/runtime/bin/process_macos.cc" and friends to handle TARGET_OS_TV functions.
https://github.com/dart-lang/sdk/blob/master/runtime/bin/process_macos.cc#L164

@devoncarew can you re-open? I don't have permissions.

[devoncarew]

Sure, will re-open.

[devoncarew]

See also:

• support making Apple TV apps Support making Apple TV apps flutter/flutter#2058
• flutter support for Apple Watch Flutter support for Apple Watch flutter/flutter#28901

[mkustermann]

/cc @a-siva Since it's not allowed to fork() on iOS anyways, we could exclude dart:ios Process.spawn related functionality in the runtime via if/def and reduce AOT code size. wdyt?

[manhluong]

Hi, are there updates about this issue?

I would be interested in running Dart (and not Flutter) in tvOS.

[lesnitsky]

our team was able to run a flutter app on tvOS, submit it to the testflight and get it working on a real device
I'm no longer involved in that project, so I am not sure what is the state of things currently. Last time when I checked the approach was still very messy to make it available for public usage (a lot of quirks in engine code). Everything basically boils down to getting rid of iOS-specific APIs which are not available on tvOS and tricking the flutter tool in a way it is not aware about tvOS as a target, but actually builds a tvOS app

[manhluong]

I see @lesnitsky, thank you!

I guess is the same line of thoughts for Dart only (instead of Flutter)...

[lesnitsky]

@manhluong as far as I can remember, we didn't make many changes to dart itself (if any at all). I believe we've just used different build config and those methods calling fork were stripped out (but my memories are very fuzzy)

[manhluong]

This sounds very promising @lesnitsky !

I will give it a try when I can and I will report back here.

For Dart only as this is my use case for now: no need to drag in whole of Flutter, for me, for now.

Thank you for answering me!

[lodmfjord]

Any news on this? What way did you go @manhluong ?

[a-siva]

/cc @a-siva Since it's not allowed to fork() on iOS anyways, we could exclude dart:ios Process.spawn related functionality in the runtime via if/def and reduce AOT code size. wdyt?
created #45452 to track this.

[manhluong]

@lodmfjord I switched to another project so didn't have time to try this yet.

@a-siva thank you!