{
    "_comment": "DO NOT EDIT THIS FILE BY HAND. USE 'scripts/update-status-go.sh <tag>' instead",
    "owner": "status-im",
    "repo": "status-go",
    "version": "v0.63.8",
    "commit-sha1": "e8dbc66227b98fcf91b0626c7747c58f3d8b31fb",
    "src-sha256": "16952l1zyj8bqzgb979w274d55nsihr5l0papvwkdk5i2xyps9q7"
}

{
    "_comment": "DO NOT EDIT THIS FILE BY HAND. USE 'scripts/update-status-go.sh <tag>' instead",
    "owner": "status-im",
    "repo": "status-go",
    "version": "v0.63.11",
    "commit-sha1": "9814a9a5e76b6fe7d312f45bac41990bc0467d4d",
    "src-sha256": "01j365ja4z6rm2hs5ck5az7wrx35v1sfwly8i0gldrisnnrh26dh"
}

Fix bug when coming back from background
Fix bug when coming back from background

Fixes: #11441
Fixes: #11416

The issue was due to a nil pointer exception with the
localNotificationService.
Upon upgrade it would be disabled and therefore it would not be
available.
This was due to the fact that initialization comes from the database and
not from status-react, so on upgrade it would not be available.

Signed-off-by: Andrea Maria Piana <39e16ece3c2d27e1889178b15ddb376e524032f8@gmail.com>
