Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In app messaging doesn't work in version 10.28.1 #13191

Closed
Tulakshana opened this issue Jun 26, 2024 · 8 comments
Closed

In app messaging doesn't work in version 10.28.1 #13191

Tulakshana opened this issue Jun 26, 2024 · 8 comments
Assignees
Labels

Comments

@Tulakshana
Copy link

Tulakshana commented Jun 26, 2024

Description

In app messaging doesn't work in version 10.28.1

Reproducing the issue

Steps to reproduce

  1. Install Firebase version 10.28.1 using cocoapods
    pod 'Firebase/Messaging', '10.28.1' pod 'Firebase/RemoteConfig', '10.28.1' pod 'Firebase/Auth', '10.28.1' pod 'Firebase/Crashlytics', '10.28.1' pod 'Firebase/Analytics', '10.28.1' pod 'Firebase/InAppMessaging', '10.28.1' #beta pod 'Firebase/Performance', '10.28.1'
  2. Go to in app messaging in the firebase console and create a new in app messaging campaign
  3. Install the new version of the app with Firebase 10.28.1 in a real device
  4. Run the app
  5. Copy the firebase installation id
    Installations.installations().installationID { [weak self] (id, error) in }
  6. Use the copied installation id to send a test in app message using the campaign you created in step 2

Expected result
Receive the in app message

Actual result
Does not receive the in app message

Firebase SDK Version

10.28.1

Xcode Version

15.3

Installation Method

CocoaPods

Firebase Product(s)

Analytics, Authentication, Crashlytics, In-App Messaging, Messaging, Performance, Remote Config

Targeted Platforms

iOS

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

No response

If using CocoaPods, the project's Podfile.lock

platform :ios, '15.0'

inhibit_all_warnings!

use_frameworks!

pod 'Firebase/Messaging', '10.28.1'
pod 'Firebase/RemoteConfig', '10.28.1'
pod 'Firebase/Auth', '10.28.1'
pod 'Firebase/Crashlytics', '10.28.1'
pod 'Firebase/Analytics', '10.28.1'
pod 'Firebase/InAppMessaging', '10.28.1' #beta
pod 'Firebase/Performance', '10.28.1'

target 'MyApp' do
end

target 'MyAppTests' do
end

post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '15.0'
config.build_settings['ENABLE_BITCODE'] = 'NO'
config.build_settings['ONLY_ACTIVE_ARCH'] = 'NO'
end
end
end

@rizafran rizafran added the api: inappmessaging Firebase In App Messaging label Jun 27, 2024
@rizafran rizafran self-assigned this Jun 27, 2024
@rizafran
Copy link
Contributor

Hi @Tulakshana, I wasn't able to reproduce the issue. May I know if you're clicking the Test on device button in the campaign before opening the app?

@Tulakshana
Copy link
Author

Tulakshana commented Jun 27, 2024

Yes. The template I used was the one with the image, text and CTA which appears at the centre of the screen.

@rizafran
Copy link
Contributor

Thanks for the reply, @Tulakshana. I can't seem to reproduce the issue. Could you confirm if it's also reproducible using a simulator on your end?

@Tulakshana
Copy link
Author

Mmm… it worked fine on the simulator. The simulator I used was iPhone 15 Pro (iOS 17.4). My real device is an iPhone XR running iOS 16.2. I tested an iPhone XR simulator (iOS 16.2) too and it worked fine. I’m using Xcode 15.3. The only way I can get the message on my real device is by switching to version 10.28.0

@paulb777
Copy link
Member

paulb777 commented Jul 1, 2024

The Podfile.lock file may provide a clue.

@google-oss-bot
Copy link

Hey @Tulakshana. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

@Tulakshana
Copy link
Author

@Tulakshana
Copy link
Author

The issue seems to be fixed in version 10.29.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 participants