Viber does not work after upgrading XA2 Plus to 4.3

I’ve updated to the latest Viber version (16.5.0.9) application starts up - but activation fails, still…

after following how to get logs from android by Zendesk I see the following logs when tried to enter my phone number and activate it:

trying to activate number:

11-22 20:09:57.929   164   264 D AlienEventHub: ALIEN: getVideoFrames is not supported
11-22 20:09:58.096   164   264 D AlienEventHub: ALIEN: getVideoFrames is not supported
11-22 20:09:58.104   592   592 E RemoteKeyboard: ALIEN: Keyboard shown
11-22 20:09:59.992  7652  7784 W GooglePlayServicesUtil: com.viber.voip requires the Google Play Store, but it is missing.
11-22 20:09:59.997  7652  7784 W MixpanelAPI.SysInfo: Permission READ_PHONE_STATE not granted. Property $radio will not be available.
11-22 20:10:08.184   164   264 D AlienEventHub: ALIEN: getVideoFrames is not supported
11-22 20:10:08.252   164   264 D AlienEventHub: ALIEN: getVideoFrames is not supported
11-22 20:10:08.407  7652  7784 W GooglePlayServicesUtil: com.viber.voip requires the Google Play Store, but it is missing.
11-22 20:10:08.422   592   592 E RemoteKeyboard: ALIEN: Keyboard hidden
11-22 20:10:08.448    46    46 E /system/bin/hw/android.system.suspend@1.0-service: error writing ApmOutput to /sys/power/wake_lock: Bad file descriptor
11-22 20:10:08.450    46    46 E /system/bin/hw/android.system.suspend@1.0-service: error writing ApmOutput to /sys/power/wake_unlock: Bad file descriptor
11-22 20:10:08.466  7652  7784 W MixpanelAPI.SysInfo: Permission READ_PHONE_STATE not granted. Property $radio will not be available.
11-22 20:10:08.546   164  1569 E WindowManager: App trying to use insecure INPUT_FEATURE_NO_INPUT_CHANNEL flag. Ignoring
11-22 20:10:11.312   164   264 D AlienEventHub: ALIEN: getVideoFrames is not supported
11-22 20:10:11.450   164   264 D AlienEventHub: ALIEN: getVideoFrames is not supported
11-22 20:10:11.568  7652  7801 W GooglePlayServicesUtil: com.viber.voip requires the Google Play Store, but it is missing.
11-22 20:10:11.624    46    46 E /system/bin/hw/android.system.suspend@1.0-service: error writing ApmOutput to /sys/power/wake_lock: Bad file descriptor
11-22 20:10:11.626   164  3986 E WindowManager: App trying to use insecure INPUT_FEATURE_NO_INPUT_CHANNEL flag. Ignoring
11-22 20:10:11.627    46    46 E /system/bin/hw/android.system.suspend@1.0-service: error writing ApmOutput to /sys/power/wake_unlock: Bad file descriptor
11-22 20:10:11.785    38  7803 E ResolverController: No valid NAT64 prefix (0, <unspecified>/0)
11-22 20:10:11.859  7652  7664 I com.viber.voip: Background concurrent copying GC freed 121863(6003KB) AllocSpace objects, 35(912KB) LOS objects, 48% free, 6434KB/12MB, paused 121us total 293.034ms
11-22 20:10:15.556  7652  7784 W GooglePlayServicesUtil: com.viber.voip requires the Google Play Store, but it is missing.
11-22 20:10:15.559   164   182 E InputDispatcher: Window handle Window{85e7fd u0 com.viber.voip/com.viber.voip.registration.RegistrationActivity} has no registered input channel
11-22 20:10:15.626   164   181 E WindowManager: App trying to use insecure INPUT_FEATURE_NO_INPUT_CHANNEL flag. Ignoring
11-22 20:10:15.661  7652  7784 W MixpanelAPI.SysInfo: Permission READ_PHONE_STATE not granted. Property $radio will not be available.
11-22 20:10:20.926   164   264 D AlienEventHub: ALIEN: getVideoFrames is not supported
11-22 20:10:21.103   164   264 I chatty  : uid=1000(system) InputReader identical 8 lines
11-22 20:10:21.134   164   264 D AlienEventHub: ALIEN: getVideoFrames is not supported
11-22 20:10:21.147  7652  7784 W GooglePlayServicesUtil: com.viber.voip requires the Google Play Store, but it is missing.
11-22 20:10:21.153  7652  7784 W MixpanelAPI.SysInfo: Permission READ_PHONE_STATE not granted. Property $radio will not be available.
11-22 20:10:21.162   164   182 E InputDispatcher: Window handle Window{885ca6d u0 com.viber.voip/com.viber.voip.registration.RegistrationActivity} has no registered input channel
11-22 20:10:21.331    46    46 E /system/bin/hw/android.system.suspend@1.0-service: error writing ApmOutput to /sys/power/wake_lock: Bad file descriptor
11-22 20:10:21.333    46    46 E /system/bin/hw/android.system.suspend@1.0-service: error writing ApmOutput to /sys/power/wake_unlock: Bad file descriptor

Any ide what goes wrong?