Not sure if this is a good place for this post or not, but here goes.
I reject outbound connections to meta domains at the firewall. I noticed this banking app refuses to prompt for login credentials unless I am on mobile or a public WiFi network. I watched my FW logs and noticed many rejected connections to graph[.]facebook[.]com.
I contacted their support team, but they denied the connection was their app. I shared the screenshot on this post and they closed my case without comment.
I emailed the address on the Google play store and they also denied the connection was their app. I shared the screenshot and they asked if I downloaded the app from the play store, implying the official app doesn’t do this, but of course it does.They closed my case without proper resolution as well.
Just thought I’d share this here so people know that some banks make direct connections to Facebook to share analytics, without your knowledge or informed consent, and they lie about it when called on it.
It’s probably NTP a lot of banking apps have extra protections and if it can’t determine the time from its own trusted authority it may not allow the connection.
Launchdarkly is likely a culprit as well. Just doing a background search reveals that the service allows dev teams to do A/B testing, enable new features without releasing a new version, and various other “dynamic” functions.
OP is on the wrong side of Occam’s razor
This is definitely probably it. I can’t believe more things aren’t broken by blocking launchdarkly
If you set it up correctly it defaults to a specific flag state if it can’t connect. I.e. always show the user the old treatment instead of the new if you can request the actual state of their enrollment.
They get blocked constantly and my old company just routed the requests through our domain so they’d stop getting blocked
how would that explain connection to facebook?
Is it normal that a bank app tries to connect to meta?
Meta provides a lot of other backend B2B services beyond just Facebook, Instagram, and Threads.
You think that’s the only way they have of scarfing down data? Absolutely not, they make other useful tools as well that businesses can use, because if they can’t get their info directly from you, they can get it from the people you have to regularly interact with instead.
This is gross… but also not something I’ve really thought about.
You better start thinking about it.
I know a software developer that worked for Ally when they were adding this. They all said it was a terrible idea, but were ignored. The reason they claim it’s needed is to track app installs that originate from an ad on Facebook. Since the App Store sits in between the ad click and App launch, there isn’t an easy way to track it without that. But, it shouldn’t be blocking you from logging in.
I’d bet you bottom dollar Ally is selling their customers’ financial information to Meta, and this is a manifestation of that.
So I just tested this. I’m not at home so I had to VPN in which is no issue.
- I opened graph.facebook.com and confirmed it was working
- I opened and logged in to my Ally app
- I added graph.facebook.com to my pi-hole’s black list as a regex entry
- I opened graph.facebook.com in the browser and confirmed it was blocked
- I force closed and cleared the cache on my Ally app
- I opened and logged in to my Ally app
It’s not the Meta connection that’s giving you trouble.
I added graph.facebook.com to my pi-hole’s black list as a regex entry
Yes, but did you clear the DNS cache on your device after doing this? Once the DNS lookup is done it doesn’t matter what you’ve done on your pihole. The IP is cached and pihole will not even see the query.
It’s a fair point but I’ve got two counters.
-
It was blocked in the browser, which implies there’s not a cached record for it on the device
-
The Pi-hole logs the queries it receives and I do have four separate entries for that URL today, spaced in an amount of time that does not imply automatic requests but does likely match up with my test cases.
-
Something else is going on with your setup, I block
graph.facebook.comvia DNS too and Ally works fine, both app and browser.Your screenshot looks like you’re also blocking ntp.org which could definitely screw with a banking app, and launchdarkly.com may also be the problem if they’re loading assets from that service.
LaunchDarkly essentially just serves up true/false values for services to grab. It can be useful to update code functionality without having to rebuild / recompile. However, any service that uses the launch darkly API should have a default state for their values to fall back on, so it shouldn’t cause any major issues if LaunchDarkly can’t be reached.
Try unblocking the ntp.org connections.
FYI this is why you DON’T use the banking app. Use a browser and I guarantee you won’t have this issue. Phone apps are mostly all adware bullshit at this point. Use as few apps as you possibly can. Your life will be better because of it.
File a complaint with the government. I’m not sure which agency, but there is definitely one for that.
Not in the US there isn’t
online only banking seems like a scam with extra steps
