Is this still relevant?

[Atemu]

Hi, I'm wondering whether GsfProxy is still necessary in modern Android because it hasn't seen a release in years.

The docs aren't entirely clear on this and generally appear quite outdated.

[david79111]

Well, it says gsfproxy is legacy support proxy library so I guess its for older android versions or apps that use old code that needs this

[Atemu]

I'd like some confirmation on exactly that.

[david79111]

So, dev said this:
"It is used only by old apps, so it is still useful but not in all cases."

microg/GmsCore#2623 (comment)

[Atemu]

@Sapiosenses is not a µG dev, though they appear to be knowledgeable.

Edit: You were talking about microg/GmsCore#2623 (comment).

[Sapiosenses]

So, dev said this: "It is used only by old apps, so it is still useful but not in all cases."

microg/GmsCore#2623 (comment)

Ask yourself:

That service was shutdown by Google almost 10 years ago. That means that no app today that continues to use that old push messaging API will work on any stock Android device.

Furthermore, since that is a GMS service, it will not work on any plain vanilla AOSP-based ROM which was last updated in the last 10+ years, because that functionality would have been removed from AOSP by that time already. (Google moved it to proprietary GMS/Gapps frameworks, like many other things over the years)

Literally the only way ANY app can still use that service, is on a custom ROM running microG. (Which just picks up the communication attempts and forwards them to the current push messaging service)

So then one has to ask themselves, how many apps are there still out there, written in the last ~10 years, that have specifically coded themselves to only have full functionality on a microG device for push messages?

Apps like that were probably written within the first 4 years of Android's existence, if that.

How many of those do you think people are still using??

I'd guess the number is infinitesimally small.

In short: the impact of that being entirely missing will probably go unnoticed by 99.5% of users.

If @ale5000-git thinks it would be easy to update it for A15 that's cool. But I'd be shocked if anyone actually noticed the change outside of the error message that Google added for apps targeting those old APIs on A13-A15 devices.