[Adding the offline discussion with @marc here, to benefit the community]
The documentation calls out when you’re creating your app, to create certificates for both production and development, which are used for push notifications.
This has to do with the production or development case doc: or you can use the token based authentication as discussed in option 2.
Once those certs or tokens have been created, then you need to create a provisioning profile, either production or development mode so that you can deploy the app. Once the device has been registered for development by the app, it is good only for development, not production. Then the development credentials should be set on the Notification Hub, depending on the method chosen either the p12 or p8 file.
In other words as noted here, when you build your app using a development cert, the app will generate a unique device token. This device token will not work on the production push network. When you then build your app with a distribution provisioning profile (App Store or Ad-Hoc) your device will generate a different device token for push notifications. If you try to send the development generated token to the production push SSL network, Apple's servers will reject your token.
Update from @marc - " I did get the problem solved after only using the production hub + app downloaded from testflight using appstore provision profile. And everytime i do local development then I just use the local development hub connectionstring, else cant get it work locally with my dev provision profile."