You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's been 2 days I am facing a problem of unreceive pushs notifications for an application build from a new Target (xcode).
Currently :
Android application : no problem (push received)
iOS application build from target 1 : no problem (push received)
iOS application build from target 2 : problem (push emitted successfully by FCM but never received on the phone)
Stack : ionic5.2.2 / angular 9 / capacitor 2.2.0
We use @capacitor-community/fcm with latest version.
We have generated, of course, a second firebase iOS configuration (firebase console) which is dedicated for target 2.
Note that the two targets are very new in our build process because we want to have development and production apps on each test phones :
app1 in a production mode (bundle identifier : com.something.xxx)
app2 in a development mode (bundle identifier : com.something.yyy)
For that, we just have :
duplicated the target1 for having a new one (target 2) and so having a new plist for that target.
changed the bundle identifier into xcode for target2, same as in firebase console for that ios app
downloaded the GoogleService-info.plist and added it for the target2.
checked that FirebaseAppDelegateProxyEnabled is set to NO into xcode
The push token is well received in build process and valid such as FCM sent push without errors to the dev app (target2).
platform :ios, '11.0'
use_frameworks!
# workaround to avoid Xcode 10 caching of Pods that requires
# Product -> Clean Build Folder after new Cordova plugins installed
# Requires CocoaPods 1.6 or newer
install! 'cocoapods', :disable_input_output_paths => true
def capacitor_pods
# Automatic Capacitor Pod dependencies, do not delete
pod 'Capacitor', :path => '../../node_modules/@capacitor/ios'
pod 'CapacitorCordova', :path => '../../node_modules/@capacitor/ios'
pod 'CapacitorCommunityFcm', :path => '../../node_modules/@capacitor-community/fcm'
pod 'CordovaPlugins', :path => '../capacitor-cordova-ios-plugins'
pod 'CordovaPluginsStatic', :path => '../capacitor-cordova-ios-plugins'
# Do not delete
end
target 'target1' do
capacitor_pods
pod 'Firebase/Messaging'
pod 'Firebase/Analytics'
end
target 'target2' do
capacitor_pods
pod 'Firebase/Messaging'
pod 'Firebase/Analytics'
end
After investigations, I have a real doubt concerning our capacitor.config.json because it has just one AppId key which value is the bundle identifier of our target1. So I consider that capacitor never know the second bundle identifier.
Could it be the problem ?
We have to consider that the target1 build well receive any push !
I am curious to know if you already have an app built with 2 targets on xcode ? (Two targets on xcode for the same application ?)
All other features works well in this second build...I just cannot receive pushs.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all :)
It's been 2 days I am facing a problem of unreceive pushs notifications for an application build from a new Target (xcode).
Currently :
Stack : ionic5.2.2 / angular 9 / capacitor 2.2.0
We use @capacitor-community/fcm with latest version.
We have generated, of course, a second firebase iOS configuration (firebase console) which is dedicated for target 2.
Note that the two targets are very new in our build process because we want to have development and production apps on each test phones :
For that, we just have :
GoogleService-info.plist
and added it for the target2.FirebaseAppDelegateProxyEnabled
is set to NO into xcodeThe push token is well received in build process and valid such as FCM sent push without errors to the dev app (target2).
Also here is our Podfile :
After investigations, I have a real doubt concerning our
capacitor.config.json
because it has just oneAppId
key which value is the bundle identifier of our target1. So I consider that capacitor never know the second bundle identifier.Could it be the problem ?
We have to consider that the target1 build well receive any push !
I am curious to know if you already have an app built with 2 targets on xcode ? (Two targets on xcode for the same application ?)
All other features works well in this second build...I just cannot receive pushs.
Any help is very welcome ^^
Regards
Beta Was this translation helpful? Give feedback.
All reactions