[AC-6587] Android notifications using ACS have stopped working completely

I have a bug with the Axway Cloud services regarding Android notifications. I have been discussing the problem with Joshua Quick. The problem seems account related, but may be a firebase/Google configuration problem related to the Axway service. Since we got a server error a few days ago of "Subscription not found" our app won't receive android notifications. It's odd if it is an account problem that iOS should still work, but that is indeed what it seems to be. In the new version of our app I upgraded to SDK 9.0.3 and implemented the new ti.cloudpush module v7.1.0. This was according to advise from Joshua Quick to solve a previous bug we had with notifications on Android being registered multiple times on the same device. The new updates did fix this previous bug. As part of this upgrade process we had to create a new firebase project and migrate our old GCM service to firebase. In the app this involved installing a new google-services.json file. So after these updates Android notifications seemed to work well (there is an outstanding issue of notifications not being received if the app is force restarted, but that apparently is a Google issue/bug). Since then we did a new round of testing on 6th August and during testing received a server bug. The screen grab of the server log is attached. In the Axway Dashboard the error was "Subscription not found". Since receiving this bug all Android notifications have stopped working. So to recap. All Android notifications were working. After receiving the server error described above and with no other software changes Android notifications stopped working. Please contact me directly for Axway account details.