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

iOS App using Firebase SDK unintentionally triggering website request when organically opening the app #14256

Open
lindsayok opened this issue Dec 13, 2024 · 4 comments

Comments

@lindsayok
Copy link

lindsayok commented Dec 13, 2024

Description

App Details:

  • App ID: 1174047097 (Issue is iOS specific, not happening on Android)
  • GMP App ID: 1:16212101609:ios:ffd6c252371e0605
  • Firebase Project: coolblue-mobile-app

Issue Summary:

The customer is seeing this behavior (see attached video called 'unexpected behavior) when some users open their app vs. just opening the app and not being re-directed anywhere (see attached video 'expected behavior). In the cases we know of, this unexpected behavior is happening directly as the app was opened, and not after clicking anything. The customer is unable to replicate the issue on the spot, but users are continuing to report it (note the issue is not happening on the newest version of the app)

The Customer is only using the Firebase SDK, and is not using any marketing tags or pixels. However, when looking at their App logs, they are seeing calls to Google tag manager, so it's odd that this is happening.

Debugging on customer side:

  • Turned off all ad manager banners
  • Removed any custom HTML from GTM that included this URL
  • Debugged the last updates in
  • The app - the previous update relating to anything tracking/Google/Campaign Manager was months before
  • Updated to the newest version of the Firebase SDK
  • Looked at the new banner creations - saw no issues there
  • Looked into any web views that could be triggered , they saw iFrames with Ad Interest Groups being loaded within their gtag script
  • Compared the last few versions of the app - there were no changes that could have caused this. Their latest update was enabling dark mode... so no relation to web views or tracking.
  • In their codebase they don't have any hardcoded webviews. If the user has the app installed and tries to open any Coolblue website page that starts with https://www.coolblue.nl/ , we are going to try to open it in the app. The app is responsible for the way this page is gonna be presented to the user and the navigation to this page.
  • It's not Firebase dynamic links related, as it's happening right when opening the app from the iPhone home screen.

Debugging on support side:

  • The 1547 entry is a request to www.coolblue.nl/winkelmandje. This suggests it's related to the Coolblue website.
  • Customer confirmed that GTM is being used on the website (but not in the app), which would explain why we see entries 1554/1555.
  • We know that the problematic URL is "https://www.coolblue.nl/winkelmandje?initialAppCall=1" (SS) and the core question is what is triggering the website request. The customer has web views in the app, however this also happened on the homepage where there was no web view.
  • One theory we had is that in their website GTM set-up, they’ve added an exception to prevent it from firing on this page. However, the customer doesn’t want to block the 'winkelmandje' (add to cart) page, but they could enable a trigger to block with 'initalAppCall' URLs.
  • Somehow the app, through some sort of connection (and a Google connection is honestly the only conclusion we have) is triggering an iframe or website URL from our app

Question: What is triggering the website request, and how can they remove it?

Reproducing the issue

No response

Firebase SDK Version

10.27.0

Xcode Version

15.4

Installation Method

Swift Package Manager

Firebase Product(s)

Infrastructure

Targeted Platforms

iOS

Relevant Log Output

No response

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

Expand Package.resolved snippet
Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet
Replace this line with the contents of your Podfile.lock!
@google-oss-bot
Copy link

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@paulb777
Copy link
Member

@lindsayok Thanks for filing the issue. This may be challenging to investigate without a reproduction example. I don't think that anything in Firebase redirects to links other than Dynamic Links.

To help narrow the scope, would you update the issue with the Firebase products linked into the project via SPM?

@lindsayok
Copy link
Author

Hi @paulb777 yes can do! To make sure I'm doing this properly, can you just confirm I'm understanding your ask correctly:
when you say 'Firebase products' you mean the APIs, correct? and what is SPM?

@paulb777
Copy link
Member

Hi @lindsayok Here is the list of products from the Issue template:

Screenshot 2024-12-17 at 9 22 00 AM

When the project was set up in Swift Package Manager (SPM) a subset of those products was chosen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants