```FAILURE: Build failed with an exception. * Wha...
# kotlin-native
d
Copy code
FAILURE: Build failed with an exception.

* What went wrong:
Some problems were found with the configuration of task ':multiplatform:sdks:sportsbook-sdk:embedAndSignAppleFrameworkForXcode' (type 'EmbedAndSignTask').
  - Type 'org.jetbrains.kotlin.gradle.plugin.mpp.apple.EmbedAndSignTask' 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.7/userguide/validation_problems.html#value_not_set> in the Gradle documentation.
  - Type 'org.jetbrains.kotlin.gradle.plugin.mpp.apple.EmbedAndSignTask' 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.7/userguide/validation_problems.html#value_not_set> in the Gradle documentation.
Has anyone run into this issue while trying to compile for iOS? This became a thing when we moved to 2.0 and adding
outputDirectory
to the framework configuration. Weirdly enough... if I just dont touch anything for roughly 10 minutes and retry it doesn't have this issue.
s
I'm seeing the same issue. Did you even figure out what's going @Dmitriy Tarasevich?
d
hey @Siggi Gunnarss so we are fairly certain that this caused by some cache in the gradle daemons
it seems as though if you kill all the daemons or wait roughly 10 minutes to let them die on their own (this is configurable) or restart your computer this gets cleared up
this comes up once in a while still when we switch between arm and simArm
s
Thanks for that! Strange that more people aren't seeing this. But yes, may be gradle cache related, I changed a seemingly unlrelated thing and re-ran and it worked. May have just been the daemon being re-started 👍