-
Notifications
You must be signed in to change notification settings - Fork 75
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
SDK doesn't compile with aws-crt 0.5.7 #69
Comments
It looks like you're trying to build the latest SDK with an older CRT. The latest SDK requires a crt version of at least 0.6.0 from a binary compatibility standpoint (the actual depdendency is 0.6.2 right now). |
@bretambrose When I looked at the build.gradle file for the SDK project I have checked out the CRT version is 0.5.4 so I thought it was okay. This is also the same SDK project I used with CRT 0.5.6 that worked fine. Is there a link you can give me for the correct SDK? |
Ah the gradle config hasn't been updated since the initial android build work was completed. For now, you can use the pom.xml to figure out the needed version (1.2.2 SDK requires 0.6.2 crt). I'll update the gradle file and make a new release asap. |
Thanks for updating the CRT version. I pulled the latest and saw that it was fixed. One other thing that's giving me issues is the newer version of CRT has a different artifact ID when I run the commands for Android on this page. What you have in the gradle file is: With the latest SDK checked out and CRT version 0.6.2, I am still not able to run my application. I still get the following error:
|
We've updated the android build process. Can you give it another go and let us know if it solves your issue? |
I pulled the latest from aws-iot-device-sdk-java-v2 repo on master and rebuilt the SDK. I am still having the same issue.
|
Does this affect all platforms (local) or just when you run it on a device? What about the emulator? Can you paste
With respect to (3), I worry that since loadLibraryFromJar swallows all exceptions, we may have a load failure that is masquerading as a runtime bind failure. |
Just to see if it would work, I renamed all the "null.null.null" things to be 0.6.2. I noticed that the SDK destination also changed in the local repository folder. It used to be "awssdk.iotdevicesdk" but is now "awssdk.crt.iotdevicesdk" and the version used to be 1.0.0-SNAPSHOT but is now 1.0-SNAPSHOT. I fixed all those things and I'm still having the same problem.
|
Our Android expert is out today; I'll see if he's able to take a look when he gets back in tomorrow. |
@bretambrose Any updates on this? |
@bretambrose Anything new with this? |
I've forwarded this to Justin, he should be able to take a look soon. |
I'm taking a look now. |
In order to get that output with nulls in it, git would have to be inaccessible from your build system. Is that the case? |
No, that shouldn't be the case. I've built previous versions the same way. CRT version 0.5.6 and 0.5.7 worked and generated the correct files/folders. Pulling the latest is when I've started seeing the issues |
Ok, I've done a clean build from scratch on both, with an empty maven repo locally. I fixed up the references between the CRT and IoT Device SDK packages in the above PR. Feel free to pull it and test, I have others at AWS testing as well just to make sure. Once this is merged, I'll do a new release of this library. No changes are required to the CRT package. |
Ok, the PR is merged, I'll start a release. Note that the group/artifact has changed for the android package to be consistent with other platforms, it is now |
Thanks for your help. Pulling the sdk from maven is much easier. I'm still having the same issue, however.
Previously we had dependencies for SDK and CRT (I think we had to for some reason but I'm not entirely sure why) and now I have only this for my dependency:
|
Small followup: I added the CRT dependency as well and I'm still seeing the same error:
Found the CRT dependency from this page I also had another developer try and he is seeing the same error. |
My impression was that this was resolved last week via call. Please reopen if there is still an issue. |
Unable to resolve dependency for ':app@debugAndroidTest/compileClasspath': Could not resolve software.amazon.awssdk.crt:android:0.6.2. |
I have the same issue, was any solution found for it? |
Confirm by changing [ ] to [x] below to ensure that it's a bug:
Known Issue
<prefix>-ats.iot.<region>.amazonaws.com
Describe the bug
This is the stack trace from running the application:
This is the stack trace from trying to build the SDK with the new aws-crt version:
SDK version number
SDK number: 0.5.7
Platform/OS/Hardware/Device
Samsung galaxy S9 - Oreo
To Reproduce (observed behavior)
To reproduce the first stack trace: Update the aws-crt version to 0.5.7 and try to run a sample application.
To reproduce the second stack trace: Update the build.gradle aws-crt version to 0.5.7 for iotdevicesdk and build the project.
Expected behavior
No error when running an application with the 0.5.7 version.
Logs/output
See above.
To enable logging, set the following system properties:
REMEMBER TO SANITIZE YOUR PERSONAL INFO
Additional context
Still trying to get proxy to work with the X509CredentialsProvider.
The text was updated successfully, but these errors were encountered: