Got a report from someone that was getting `embedA...

# multiplatform

[John O'Reilly]

Got a report from someone that was getting embedAndSignAppleFrameworkForXcode error (https://github.com/joreilly/PeopleInSpace/issues/263) trying to build/install PeopleInSpace app to physical iOS device. We see same error if you say try to archive. More in thread....

[John O'Reilly]

this is key part of logs....just in case anyone has come across this...

> Task :common:embedAndSignAppleFrameworkForXcode FAILED
error: Some problems were found with the configuration of task ':common:embedAndSignAppleFrameworkForXcode' (type 'FrameworkCopy').

FAILURE: Build failed with an exception.

* What went wrong:
Some problems were found with the configuration of task ':common:embedAndSignAppleFrameworkForXcode' (type 'FrameworkCopy').
  - In plugin 'org.jetbrains.kotlin.gradle.scripting.internal.ScriptingKotlinGradleSubplugin' type 'org.jetbrains.kotlin.gradle.plugin.mpp.apple.FrameworkCopy' property 'destinationDirectory' doesn't have a configured value.
    
    Reason: This property isn't marked as optional and no value has been configured.
    
    Possible solutions:
      1. Assign a value to 'destinationDirectory'.
      2. Mark property 'destinationDirectory' as optional.
    
    For more information, please refer to <https://docs.gradle.org/8.4/userguide/validation_problems.html#value_not_set> in the Gradle documentation.
  - In plugin 'org.jetbrains.kotlin.gradle.scripting.internal.ScriptingKotlinGradleSubplugin' type 'org.jetbrains.kotlin.gradle.plugin.mpp.apple.FrameworkCopy' property 'sourceFramework' doesn't have a configured value.
    
    Reason: This property isn't marked as optional and no value has been configured.
    
    Possible solutions:
      1. Assign a value to 'sourceFramework'.
      2. Mark property 'sourceFramework' as optional.
    
    For more information, please refer to <https://docs.gradle.org/8.4/userguide/validation_problems.html#value_not_set> in the Gradle documentation.

[John O'Reilly]

This had definitely been working before so likely a regression.....perhaps related to newer versions of some of dependencies now being used

[Osman Saral]

hi @John O'Reilly i'm having the same issue right now. do you remember what was the solution?

[Osman Saral]

I tried your solution on your pr but it didn't work