Status-react: syncing issue? been 10+ mins, can see incoming transaction but Status geth node doesnt see it

[jarradh]

Device: samsung SM-G935F, OS Level 23

Memory: 2355.0/3562.0 MB

Storage: 15.313/25.44 GB

Battery: 100, Charging through USB cable

App Version: 1.0 (1)

Duration: 9

Console Log:

8817): Handling re-frame event: :update-sync-state
11-20 19:16:40.297 I/ReactNativeJS( 8817): Handling re-frame event: :update-sync-state
11-20 19:16:40.807 I/ReactNativeJS( 8817): Handling re-frame event: :update-sync-state
11-20 19:16:41.327 I/ReactNativeJS( 8817): Handling re-frame event: :update-sync-state
11-20 19:16:41.847 I/ReactNativeJS( 8817): Handling re-frame event: :update-sync-state
11-20 19:16:42.367 I/ReactNativeJS( 8817): Handling re-frame event: :update-sync-state
11-20 19:16:42.867 I/ReactNativeJS( 8817): Handling re-frame event: :update-sync-state
11-20 19:16:43.397 I/ReactNativeJS( 8817): Handling re-frame event: :update-sync-state
11-20 19:16:43.907 I/ReactNativeJS( 8817): Handling re-frame event: :update-sync-state
11-20 19:16:44.027 D/SensorManager( 8817): unregisterListener ::   
11-20 19:16:44.027 V/ActivityThread( 8817): updateVisibility : ActivityRecord2eb5beb token=android.os.BinderProxy@5288308 im.status.ethereum/im.status.ethereum.MainActivity show : true
11-20 19:16:44.127 I/System.out( 8817): (HTTPLog)-Static: isSBSettingEnabled false
11-20 19:16:44.127 I/System.out( 8817): (HTTPLog)-Static: isSBSettingEnabled false
11-20 19:17:38.427 D/StatusModule( 8817): Send module.initialized event
11-20 19:17:38.427 I/ReactNativeJS( 8817): Handling re-frame event: :signal-event
11-20 19:17:38.427 D/ReactNativeJS( 8817): DEBUG [status-im.handlers:110] - :event-str type:module.initialized
11-20 19:17:38.427 I/ReactNativeJS( 8817): Handling re-frame event: :status-module-initialized!
11-20 19:17:38.487 D/SensorManager( 8817): registerListener :: 0, K6DS3TR Acceleration Sensor, 200000, 0,  
11-20 19:17:38.497 I/ReactNativeJS( 8817): Handling re-frame event: :update-sync-state
11-20 19:17:38.517 I/Timeline( 8817): Timeline: Activity_idle id: android.os.BinderProxy@5288308 time:164121181
11-20 19:17:38.517 I/System.out( 8817): (HTTPLog)-Static: isSBSettingEnabled false
11-20 19:17:38.517 I/System.out( 8817): (HTTPLog)-Static: isSBSettingEnabled false
11-20 19:17:39.537 D/ViewRootImpl( 8817): ViewPostImeInputStage processPointer 0
11-20 19:17:40.127 D/ViewRootImpl( 8817): ViewPostImeInputStage processPointer 1
11-20 19:17:42.167 I/art     ( 8817): Background sticky concurrent mark sweep GC freed 6315(330KB) AllocSpace objects, 6(120KB) LOS objects, 2 free, 27MB/27MB, paused 6.297ms total 44.539ms
11-20 19:17:47.647 I/INSTABUG - a( 8817): invokeGeneral
11-20 19:17:47.647 I/Timeline( 8817): Timeline: Activity_launch_request id:im.status.ethereum time:164130313
11-20 19:17:47.867 I/INSTABUG - a( 8817): invokeGeneral
11-20 19:17:47.867 I/Timeline( 8817): Timeline: Activity_launch_request id:im.status.ethereum time:164130534
11-20 19:17:47.877 D/SensorManager( 8817): unregisterListener ::   
11-20 19:17:47.877 D/RelationGraph( 8817): garbageCollect()
11-20 19:17:47.877 W/ResourcesManager( 8817): getTopLevelResources: /data/app/im.status.ethereum-1/base.apk / 1.0 running in im.status.ethereum rsrc of package im.status.ethereum

Current View: im.status.ethereum.MainActivity

[jarradh]

This probably has to do with the testnet reset

currently my device is on and its eth.blockNumber = 1886418 but testnet is actually on 5211

[jarradh]

maybe we should have a !reset command in console to purge the blockchain somehow @farazdagi

[jarradh]

also in regards to auto-updating transaction list, we should poll the getBalance of account and when it changes on blockchain then we update the transaction list - so they are not out of sync (plus we can poll faster locally)
@adrian-tiberius

[jarradh]

can confirm removing the chaindata fixies syncing issue

[farazdagi]

• @jarradh well it can be done (reset will be scheduled, and node forced to restart) https://github.com/status-im/status-go/issues/63
• yep Morden -> Ropsten move is in progress https://github.com/ethereum/go-ethereum/pull/3315 I will make sure I apply this patch on our test servers (I suppose they will merge that PR quickly, but will not wait for it), and reset their chain data (so that they resync - shouldn't take long as we are at ~6K block)

[jarradh]

thanks @farazdagi

[obscuren]

You can also use ropsten without the linked PR. You can:

1. curl -O https://dl.dropboxusercontent.com/u/4270001/testnet_genesis.json
2. geth --datadir /tmp/new_testnet init <above_file>
3. start geth with geth --datadir /tmp/new_testnet --networkid 3

(1) fetches a new custom genesis file with the correct chain configuration (2) initialises a new chain using said file (3) starts the new geth node with networkid 3, which is used for the new test net.