Error on Android platform about flow-java-client-example HOT 15 OPEN

Nice desktop background.

Here's the link in that screenshot

Will look into it.

from flow-java-client-example.

Issue is being worked on here: https://github.com/the-nft-company/flow-jvm-sdk/tree/android-crypto

from flow-java-client-example.

Hello, relying on the Android-Crypto branch, there is a new problem

from flow-java-client-example.

We're going to have to create a completely different crypto implementation for android. Really all that's required for using the SDK is implementations of Signer and Hasher.

from flow-java-client-example.

@briandilley Thank you for wanting to let me know when it's fixed

from flow-java-client-example.

@briandilley We're going to have to create a completely different crypto implementation for android. Really all that's required for using the SDK is implementations of Signer and Hasher.

At present, I cannot correctly use Flow creation and transaction on Android phone. May I ask when the problem of appeal can be fixed? Worried about something

from flow-java-client-example.

AndroidCrypto signature caused the above problems in the test network, Java platform is normal, can help fix the android platform to create accounts and transactions

from flow-java-client-example.

isn't P-256 should be secp256r1 ?

from flow-java-client-example.

isn't P-256 should be secp256r1 ?

There is no problem with the business code, the same set of code should not appear correctly on the Jave platform, but the above error occurs on the Android platform

from flow-java-client-example.

@LB6264 I meant for Android, I maybe wrong, but I think P-256 is named as secp256r1 on Android, can you try with secp256r1instead of P-256 ? You can change it in SDK code, and try if it works. ( I don't have access to Android tooling unfortunately right now )

from flow-java-client-example.

@LB6264 I meant for Android, I maybe wrong, but I think P-256 is named as secp256r1 on Android, can you try with secp256r1instead of P-256 ? You can change it in SDK code, and try if it works. ( I don't have access to Android tooling unfortunately right now )

signAlgo=ECDSA_P256, hashAlgo=SHA3_256, weight=1000, sequenceNumber=78 The key is ECDSA_P256, can not be simply changed to secP256R1 directly, and this does not solve the problem, the essence is also android signature problem, I wonder if there is a solution to fix this part?

from flow-java-client-example.

signAlgo=ECDSA_P256, hashAlgo=SHA3_256, weight=1000, sequenceNumber=78 The key is ECDSA_P256, can not be simply changed to secP256R1 directly, and this does not solve the problem, the essence is also android signature problem, I wonder if there is a solution to fix this part?

what I meant was:

src/main/kotlin/org/onflow/sdk/models.kt line 62
P-256 -> secp256r1

from flow-java-client-example.

signAlgo=ECDSA_P256, hashAlgo=SHA3_256, weight=1000, sequenceNumber=78 The key is ECDSA_P256, can not be simply changed to secP256R1 directly, and this does not solve the problem, the essence is also android signature problem, I wonder if there is a solution to fix this part?

what I meant was:

src/main/kotlin/org/onflow/sdk/models.kt line 62 P-256 -> secp256r1

I have tried, and still report the same error

[Error Code: 1006] invalid proposal key: public key 0 on account 2d86961881b70678 does not have a valid signature: [Error Code: 1009] invalid envelope key: public key 0 on account 2d86961881b70678 does not have a valid signature: signature is not valid

from flow-java-client-example.

There is signature in the transaction, so it is signing. You should not obfuscate Flow classes also just keep in mind.

from flow-java-client-example.

There is signature in the transaction, so it is signing. You should not obfuscate Flow classes also just keep in mind.

At present, it is the android platform signature problem. I haven't solved it yet, so I hope the official solution can be found

from flow-java-client-example.