-
Notifications
You must be signed in to change notification settings - Fork 0
Build error during archiving web3swift #15
Comments
Hello @6epreu This pod is arm64 only due to secp256k1 pod being 64 bit only and BigInt bug (I believe it used non-fixed Uint size the last time I've checked 32 bit build). Sincerely, Alex |
according spec of secp256k1 I can see that it supports all architectures, not only arm64. |
Would you try the same procedure with 0.3.0 pod? It's marked as "64 bit only" pod and I believe your project should automatically set those as ones that used while archiving. In principle I've also updated secp256k1 to remove 64 bit only requirements. I'll also test a behavior of 32 bit build to check if BigInt was fixed. Sincerely, Alex. |
I have a same issue on 0.3.5. It has been fixed after update to 0.4.0 |
Would you also try 0.5.0?
…________________________________
From: mewehk <notifications@github.com>
Sent: Wednesday, April 11, 2018 8:40:09 AM
To: BANKEX/web3swift
Cc: Alexander; Comment
Subject: Re: [BANKEX/web3swift] Trying to create archive with web3swift (#15)
I have a same issue on 0.3.5. It has been fixed after update to 0.4.0
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#15 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AGKv97GwKcg7_lNb0HtwYm589JlgWPojks5tnZc5gaJpZM4SSXuR>.
|
Closing due to inactivity |
Archive is ok. But I have a runtime problem #62 |
Thanks for reprt, @mewehk |
I was facing same issue during archiving webs3swift . But it was done after 4 hours .It take to much time. |
We moved our development to the new repo |
Hello web3swift team.
When Im trying to archive project Im getting this errors.
Im using Generic iOS device as a device target and by default release build scheme to compile.
It seems to me because you support only arm64 architecture as I can see in your pod build target.
Library in pod - web3swift (0.2.12):
Please comment what can exactly be wrong
The text was updated successfully, but these errors were encountered: