outblock/fcl-swift

fcl-swift's Issues

Call fcl.mutate always fail

Hi,

I just started learning Flow blockchain and building an iOS dApp refer to this article https://dev.to/theagilemonkeys/how-to-buid-a-native-ios-dapp-that-uses-the-flow-blockchain-as-the-backend-n9k

I run FCLDemo(0.0.3) and try to trigger SendTransaction but it always returns the error(decode failed). I debug and found out the error return from AccountsResolver when it tried to call executePost request pre_authz(https://flow-wallet-testnet.blocto.app/api/flow/pre-authz) service API and got the response Invalid domain - HTTP status code: 400

It's happened on both testnet and mainnet (blockto wallet)

The fcl.config is same as what the FCLDemo setup

Sometime authn request still polling

Send FCL version and language in `authn` request

In the initial authn request to the Wallet, it would be helpful if the fcl version and language were sent to the Wallet, so that the Wallet can return a response appropriate for that version. It is also helpful for logging purposes. In fcl-js, this body is sent in the initial authn request. fcl-swift should send something similar:

{
  "fclVersion": "0.0.78-alpha.10",
  "service": {
    "type": "authn"
  },
  "config": {
    "discoveryAuthnInclude": [],
    "services": {},
    "app": {
      "title": "My awesome app",
      "icon": "http://my.awesome.app/logo.png"
    }
  },
  "timestamp": 1643678060750,
  "appDomainTag": "MyAwesomeApp",
  "extensions": []
}

The fclVersion value could be augmented with the package name, such as @outblock/[email protected]

Package url referring to wrong repo

The package url in Package.swift is referring to the wrong repo, which makes adding the package to a Swift app confusing. The README also refers to zed-io.

Add user-agent to http-headers

See this for format: https://khorbushko.github.io/article/2021/06/05/user-agent.html

Change the SFViewController modal from full screen to sheet

Breaking changes in Cadence

Hello Flow SDK maintainer! We need your help updating this repository ASAP. Please check the last change in this post about breaking changes coming along with the release of Secure Cadence and read the documentation about this specific change.

`authenticate` request should include `timestamp` and `appDomainTag` so that wallet provider can return an `account-proof` service

fcl-swift should include timestamp and optionally appDomainTag so that the Wallet provider can return an account-proof services as outlined in this spec