When clicking on "Create Token" we can see this request sent to CP:
When clicking on "Yes" in confirm issuance we see this request:
Second request is indeed the one signed and broadcasted.
In red, the fee for the first request used for estimation, value in sats. In blue the fee effectively used for the final TX, value in BTC => As createIssuance do parseInt on fee parameter, you get parseInt('0.00xxx') which results to zero.
Final tx for issuance always use 0 for tx fee.
Using local version of FW with master.
When clicking on "Create Token" we can see this request sent to CP:
When clicking on "Yes" in confirm issuance we see this request:
Second request is indeed the one signed and broadcasted.
In red, the fee for the first request used for estimation, value in sats. In blue the fee effectively used for the final TX, value in BTC => As createIssuance do parseInt on fee parameter, you get parseInt('0.00xxx') which results to zero.