-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation Issue using AWSPinpoint on iOS target with watch target #1279
Comments
@lawmicha I'm on the AWS SDK for Swift team, and I'm looking into this. I created a Apple Watch project in Xcode, and was able to reproduce this failure as you described. I'm not deeply familiar with Apple Watch development; is it normal to compile for 32 bits? (see your failed compile command above, the failed compile seems to be for |
After a little Google searching and a little experimenting in Xcode:
I was able to get the watch app to run on my desktop but the change to DWARF settings may impair the ability to debug the app. In the meantime, we will continue to investigate. |
@lawmicha Because this issue is wider than just AWS Pinpoint, I have filed a more general ticket to address watchOS compilation challenges: #1283. If you don't have anything else specific to AWS Pinpoint, and the DWARF settings fix above unblocks you for the interim, I'm going to close this ticket & keep #1283 open until the root causes are addressed. We are starting to take a closer look at platform-specific issues like this as we approach GA, so please feel free to file tickets for any other platform-specific problems you encounter. |
Hi @jbelkins, thanks for looking into this
It seems like this is expected. I couldn't find some definitive answers about watchOS architecture but we mainly observed the behavior that Int is 32-bit at runtime of the app on a watch device. In the related issues, we ended up doing size checks before creating the Int or swapping it out to use Int64 or UInt64. There was one SO link that mentioned arm64_32 has 32-bit pointer sizes
|
Great findings, thanks for the workaround! I'll pass it along to aws-amplify/amplify-swift#3312 Feel free to close this issue and we'll track #1283 |
Describe the bug
Over in the Amplify repo, we got an issue related to compiling AWSPinpointAnalyticsPlugin as a dependency for an iOS target which embeds a watch target.
Issue: aws-amplify/amplify-swift#3312
Expected Behavior
No compilation issues
Current Behavior
Reproduction Steps
ATM I didn't do this directly with the AWS SDK for Swift, but I think it should be reproducible since Amplify's AWSPinpointPlugin doesn't depend on much other than Swift SDK's AWSPinpoint. Here are the steps from aws-amplify/amplify-swift#3312
Possible Solution
Possibly pull in @atierian as he may have some ideas here (see comment aws-amplify/amplify-swift#3312 (comment))
The customer thinks the file may be too big: aws-amplify/amplify-swift#3312 (comment)
Maybe we need to keep track of the line limit and split the split the generated file into extension files? I'm not sure of the architecture so hard to suggest a fix
Additional Information/Context
No response
AWS SWIFT SDK version used
0.31.0"
Compiler and Version used
Xcode 15.1 RC (15C65)
Operating System and version
macOS
The text was updated successfully, but these errors were encountered: