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

Upstream merge #1

Merged
merged 45 commits into from
Sep 25, 2023
Merged

Upstream merge #1

merged 45 commits into from
Sep 25, 2023

Conversation

Daviteusz
Copy link

@Daviteusz Daviteusz commented Sep 23, 2023

I resolved repo incompatibility and translated two items in -base

mar-v-in and others added 30 commits August 29, 2023 11:33
Needs slightly more time if apps take care of only registering one bitmap once but saves a lot of time and memory when they don't (and many don't)
Also handle empty strings from apps as none.

Fixes microg#2021, microg#2022
This puts the base to allow apps that allow/require sign in with Google Play Games to work.
Note that as the Play Games companion app is not functional (yet), many features of Play Games remain unusable.
It's a PendingIntent, so that doesn't work and spills a warning.

Fixes microg#2029
This is the same as in fake-store. Soon we'll have to move FakeStore/Companion
to this repository anyway (so that it can access certain parts from core needed
to support IAP and PI), until then it's probably fine to have this code
duplicated.
Server says >> "" is not a valid serial number <<, but null is fine 🤷
And fix the bugs found by that
This fixes a crash in the sample app
We lost them when moving from safe-parcel module
…lection

This improves speed and should help against ProGuard optimizing away our code
This is useful for apps that include microG as a library, so they can easily
modify the default configuration of their embedded microG.
- Nearby can now be configured through local build property, enabled by default
- Exposure Notifications is not displayed in settings if not used for >14 days
- Flavors per map type remain (but moved maps implementations)
…gnature

Moving the vending app here is also in preparation for support for various
features that have to be provided in the com.android.vending package like
IAP, Play Integrity, Split Install, ...
This may limit functionality (e.g. the device might be unable to act as a
privileged device in the authentication system), but allows to register on
devices that are not registered in Google's system.
This is disabled by default, as it currently relies on a non-free library. It
can be enabled by setting modules.hms=true in local.properties. You also need
to place your agconnect-services.json and set hmsmap.key in local.properties.
@SpacingBat3
Copy link
Owner

Looks OK. I don't see any new strings translated though, I've only noticed some strings to be actually moved to -base from the previous location.

@SpacingBat3 SpacingBat3 merged commit 9556c79 into SpacingBat3:upstream-merge Sep 25, 2023
1 check failed
@SpacingBat3
Copy link
Owner

Also thx for helping me with keeping this repo fresh! I've also translated new -vending strings. I've also noticed microG is setting up localization via https://www.transifex.com/, or at least that's what newly added config suggests.

@Daviteusz
Copy link
Author

Looks OK. I don't see any new strings translated though, I've only noticed some strings to be actually moved to -base from the previous location.

Ah sorry, I translated them while resolving conflicts and this is why they hard to find :D
https://github.com/microg/GmsCore/blob/753fbd6c0aadfec1ce1a1f4b8e46fea6a297787b/play-services-base/core/src/main/res/values-pl/strings.xml#L23C7-L23C7
They were On and Off in play-services-core/src/main/res/values/strings.xml. Perhaps I should do it later as a separate commit.

Also thx for helping me with keeping this repo fresh! I've also translated new -vending strings. I've also noticed microG is setting up localization via https://www.transifex.com/, or at least that's what newly added config suggests.

At this moment, the configuration file has been deleted, so it's hard to tell 😃

@SpacingBat3
Copy link
Owner

Ah sorry, I translated them while resolving conflicts and this is why they hard to find :D microg/GmsCore@753fbd6/play-services-base/core/src/main/res/values-pl/strings.xml#L23C7-L23C7 They were On and Off in play-services-core/src/main/res/values/strings.xml. Perhaps I should do it later as a separate commit.

Wasn't that defined in play-services-core previously? The diff seems to tell this was done before (+ I remember myself localizing that before):
https://github.com/SpacingBat3/GmsCore/pull/1/files#diff-41fd28704cd51671fd8c58dbd62544ba4f5fc22f0987b8b0009917bf623adcf8L51-L57

Outside of this, I haven't noticed any changes to localizations done, so I guess this PR indeed only resolved the conflicts. But still there were some leftovers left and I'm not sure if there are any additional items added in existing locales after you merged the upstream.

@Daviteusz
Copy link
Author

Hmm... It seems that was something strange happened on my vscode and I had to add these two lines manually, I took them from -base .../values/strings.xml, I was wondering whether to translate them as Wył or Wł. Wył. I selected second variant, then I pushed out changes and made this PR :D

According to the commit history this translation was already there, so in that case that's why my changes are not visible, because they are identical, so you are correct, this is only upstream merge, nothing else 😂

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

Successfully merging this pull request may close these issues.

5 participants