Incorrect error: "Topic is not allowed" after sending notification

**Describe the bug**
After a sucessfull push, if you try to send a second push with another certificate, bundle id, etc. an error "Pushing to this topic is not allowed". So you have to restart the app and then try the last push and now it works.

**To Reproduce**
- Fill the form with a p12 credentials authentication, passphrase, and the other needed data, and check that the push is sent successfully.
- Now try another app (different bundle id, certificate and device token) and the app throws the error "Pushing to this topic is not allowed".
- Restart the app and send the last push, now there is no error, the push is correctly sent.

**Expected behavior**
The app have to be able to save multiple push configurations and be able to test different app pushes without close and restart the app, simply switching between the configuration, or changing the current configuration.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

**Additional context**
Add any other context about the problem here.

Start by reproducing the second-push failure in the macOS app while switching the p12 credentials, bundle ID, and device token without restarting. Trace the push configuration form through the notification-sending flow; done means multiple configurations can be changed or saved and successive pushes use the selected configuration without requiring an app restart.

Written by the indexing model from the issue text.