cosmostation / cosmostation-android Goto Github PK

Right now I am using cosmostation to test out using WalletConnect v2 with our dapp. Secret network mainnet secret-4 works great. But, I would like to test out our dapp which is only deployed on testnet pulsar-2 atm.

Cosmostation just crashes when I request cosmos:pulsar-2 with a walletconnect deeplink right now.

what the hell... thanks a lot for your solution, got the same problem

Originally posted by @alex0005 in signalapp/Signal-Desktop#2483 (comment)

Hi,

I've tried to use Wallet Connect for the first time by clicking the button I'm getting Preparing... and nothing more, but all 3 app permissions granted.

Do anybody know the reason why WalletConnect doesn't work on my Samsung android version: 9 and Cosmostation: v1.5.45, or just a general issue with this app?

This issue happens whenever I try to go into the delegate tab and select any option right after refreshing the data.
This was the log when app crashed.

time: 1642750390222
msg: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.TextView.setText(java.lang.CharSequence)' on a null object reference
stacktrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{wannabit.io.cosmostaion/wannabit.io.cosmostaion.activities.ReInvestActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.TextView.setText(java.lang.CharSequence)' on a null object reference
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3635)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3792)
	at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:103)
	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2210)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:201)
	at android.os.Looper.loop(Looper.java:288)
	at android.app.ActivityThread.main(ActivityThread.java:7835)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:550)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.TextView.setText(java.lang.CharSequence)' on a null object reference
	at wannabit.io.cosmostaion.activities.ReInvestActivity.onCreate(ReInvestActivity.java:59)
	at android.app.Activity.performCreate(Activity.java:8050)
	at android.app.Activity.performCreate(Activity.java:8030)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1332)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3608)
	... 12 more

In the Cosmostation android app under "My Deposited Value" in the Kava DeFi - Pool tab, the values of the new LP coins are not being reflected when calculating the total amount the user deposited. It reflects the amount of USDX deposited but not ATOM, OSMO, LUNA and so forth. It calculates correctly for native pairs though. I am running v1.5.47 of the app. This issue applies to the "Total Deposited Value" as well.

The crash happened only once. In next two subsequent voting, there was no issue.
This was the stack trace and message when the app crashed.

msg: java.lang.NullPointerException: Attempt to invoke virtual method 'void wannabit.io.cosmostaion.base.BaseFragment.onRefreshTab()' on a null object reference
--
  | stacktrace: java.lang.NullPointerException: Attempt to invoke virtual method 'void wannabit.io.cosmostaion.base.BaseFragment.onRefreshTab()' on a null object reference
  | at wannabit.io.cosmostaion.activities.VoteActivity$1.onPageSelected(VoteActivity.java:94)
  | at androidx.viewpager.widget.ViewPager.dispatchOnPageSelected(ViewPager.java:1947)
  | at androidx.viewpager.widget.ViewPager.setCurrentItemInternal(ViewPager.java:665)
  | at androidx.viewpager.widget.ViewPager.setCurrentItemInternal(ViewPager.java:631)
  | at androidx.viewpager.widget.ViewPager.onRestoreInstanceState(ViewPager.java:1462)
  | at android.view.View.dispatchRestoreInstanceState(View.java:21018)
  | at android.view.ViewGroup.dispatchRestoreInstanceState(ViewGroup.java:4000)
  | at android.view.ViewGroup.dispatchRestoreInstanceState(ViewGroup.java:4006)
  | at android.view.ViewGroup.dispatchRestoreInstanceState(ViewGroup.java:4006)
  | at android.view.ViewGroup.dispatchRestoreInstanceState(ViewGroup.java:4006)
  | at android.view.ViewGroup.dispatchRestoreInstanceState(ViewGroup.java:4006)
  | at android.view.View.restoreHierarchyState(View.java:20996)
  | at com.android.internal.policy.PhoneWindow.restoreHierarchyState(PhoneWindow.java:2225)
  | at android.app.Activity.onRestoreInstanceState(Activity.java:1723)
  | at android.app.Activity.performRestoreInstanceState(Activity.java:1676)
  | at android.app.Instrumentation.callActivityOnRestoreInstanceState(Instrumentation.java:1379)
  | at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3676)
  | at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
  | at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
  | at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
  | at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
  | at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2210)
  | at android.os.Handler.dispatchMessage(Handler.java:106)
  | at android.os.Looper.loopOnce(Looper.java:201)
  | at android.os.Looper.loop(Looper.java:288)
  | at android.app.ActivityThread.main(ActivityThread.java:7835)
  | at java.lang.reflect.Method.invoke(Native Method)
  | at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:550)
  | at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)

title
v. 1.10

Right now on current version, using a starname for recipient only resolves IOV ( Starname specific ) address properly and fails to resolve for other chains, which was working before.

Currently it errors out with a message: "Valid starname, but no matching address with this chain", where the starname actually is having a valid matching address specific to chain under asset:{denom}

It should be fixed taking asset resource denom map into consideration from resources after resolving a starname

Other applicable project https://github.com/cosmostation/cosmostation-ios

Ref:
Asset Ticker list - Starname Documentation
https://api.iov-mainnet-ibc.iov.one/swagger/#/Query/Starname

Something is wrong with the latest wallet. It updated on android, but it did not import the correct wallet address for Medibloc.
Previous address for Medibloc wallet is different from the one that's now on there and the coin count is 0.
When I check the prior address on the explorer the coins are still there on the prior address. There is no option on the Medibloc wallet to import the prior address.

The other wallets I notice have the prior address, such as Comos and Akash. Only Medibloc.

On latest android.
When removing liquidity from Kava earn, I get a fee bug. I am attempting to remove the max amount of liquidity I can by using the Max button.
I currently have 0.9 Kava in the wallet, so it should work.

I tried again with slightly less than the max and it worked, but now I still have some in the pool.

Huahua asset value shown in the app is very different than when calculating the value on CMC or coingecko. The indicated total value is currently about 10% lower than. The actual value.

evmos/evmos#1691

Ledger (via BT) is only available currently for Atom and Osmosis, would be nice to add other tokens as well!

When connected to the Kava dapp in Cosmostation app there is a bug when casting a vote. It says "error during broadcasting
Signature verification failed please verify. account number " however voting on kava works normally from the wallet tab governance button
I only get the error when connected to the dapp connected via wallet connect.

Like from https://osmosis.zone/ I can connect keplr wallet.
In cosmostation, is there any feature to connect keplr wallet ??

Starnames with pattern: name*domain work at time of starname resolution but starnames with pattern: *domain doesn't work
It shows Unregistered name service error

    <string name="error_invalid_icns">Unregistered NameService.</string>

yarn
yarn add @cosmostation/extension

npm
npm install @cosmostation/extension

While redelegating, I get the out of gas error for Osmosis if I don't press the "Check Estimate Gas Amount" button to simulate the transaction before actually proceeding with the transaction. This has been happening a lot lately for Osmosis.

I guess it would be better if onSetFee is also called on refresh for Osmosis too, just like it is being done for Evmos as of now in the onRefreshTab() in StepFeeSetFragment. This would eliminate the hassle for an average user.

    else if (getSActivity().mBaseChain.equals(BaseChain.OSMOSIS_MAIN)) {
            onSetFee(mSelectedGasDenomPosition);
            onCheckTxType();
        }

what the hell... thanks a lot for your solution, got the same problem

Originally posted by @alex0005 in signalapp/Signal-Desktop#2483 (comment)

Hello,

I'm trying to connect wallet on cosmostation from my native android dapp using wallet connect. After calling Intent, wallet connect showing only few apps like metamask, trustwallet etc. Not showing cosmostation inside the app chooser.
Is there any possibility to connect cosmostation wallet using deep linking(Wallet connect) from native android app?

Regex for checking a valid account name, valid domain name has been updated by Starname
Current one can be viewed here: Starname Params

Please update:

This is causing some new names to fail at starname resolution step at Send or related interfaces
Manually updating the regex will fix this in my opinion, but a better solution would be to get this from the api itself, as its kinda core to cosmostation

After checking out the project locally (master branch), I tried running the project. I receive this error on build:

`FAILURE: Build completed with 2 failures.

1: Task failed with an exception.

• What went wrong:
  Execution failed for task ':app:processDebugGoogleServices'.

File google-services.json is missing. The Google Services Plugin cannot function without it.
Searched Location:
path\app\src\nullnull\debug\google-services.json
path\app\src\debug\nullnull\google-services.json
path\app\src\nullnull\google-services.json
path\app\src\debug\google-services.json
path\app\src\nullnullDebug\google-services.json
path\app\google-services.json

• Try:
  Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
  ==============================================================================

2: Task failed with an exception.

• What went wrong:
  Execution failed for task ':app:validateSigningDebug'.

Keystore file 'path\app\debug.keystore' not found for signing config 'debug'.

• Try:
  Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
  ==============================================================================

• Get more help at https://help.gradle.org
  `

Can you help me? I have read the Readme but did not find any information about this.

Thanks!

Ref: https://gitlab.com/fdroid/rfp/-/issues/2059

Where do these libs come from? https://github.com/cosmostation/cosmostation-android/tree/master/app/libs

/LE: Can these non-FOSS deps be separated? Say in a gradle flavor?
https://github.com/cosmostation/cosmostation-android/blob/master/app/build.gradle#L94-L95
https://github.com/cosmostation/cosmostation-android/blob/master/app/build.gradle#L132
What are they used for anyway?

When a kava wallet is loaded it shows the balance of the incentives for liquid staking. If another tab is clicked on then clicked back to the main tab it has an incentive display error. I tested it out and got it to display that I had 100 Kava waiting to be claimed when I only had .05 I wouldn't say it is a big issue but it is annoying.

Following is the response after broadcast:

{"memoizedIsInitialized":1,"txResponse_":{"code_":0,"codespace_":"","data_":"","gasUsed_":0,"gasWanted_":0,"height_":0,"info_":"","logs_":[],"memoizedIsInitialized":-1,"rawLog_":"[]","timestamp_":"","txhash_":"4BEB089FF4DD0F6282605BCF2A7F6F472578FBD39B36F47D4A597B5D0463A00","unknownFields":{"fields":{},"fieldsDescending":{}},"memoizedSize":-1,"memoizedHashCode":0},"unknownFields":{"fields":{},"fieldsDescending":{}},"memoizedSize":-1,"memoizedHashCode":0}