Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Clarify four PrivacyInfo data categories for basic sign-in in GoogleSignIn-iOS 10.0.0

Offen
  • Stimmt etwas nicht?
#647 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Dokumentation
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
ios, objective-c
Bereich
authentication, documentation

Rechercherichtung

Start with the referenced PrivacyInfo.xcprivacy at commit 7823e518f5d4db765ccac3e140dd3265ef0a1cf1 and compare its four named categories with the linked iOS sign-in privacy guide and issue #646 comment. Clarify collection, component, purpose, linkage, tracking, and whether the manifest covers possible integrations for basic sign-in; done when official guidance answers each question for version 10.0.0.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug triage

We use GoogleSignIn-iOS 10.0.0, pinned at commit 7823e518f5d4db765ccac3e140dd3265ef0a1cf1, for basic Google sign-in on iOS with email/profile only. We do not request phone-related or other additional scopes, and we do not implement phone/SMS authentication.

The SDK's PrivacyInfo.xcprivacy declares PhoneNumber, DeviceID, OtherUsageData, and OtherDataTypes in addition to categories discussed in the iOS sign-in privacy guide. The guide describes user identifiers and IP-derived location, but does not clarify how these four categories apply to a basic sign-in integration.

Could you clarify, for each of these four categories:

  1. Is the data collected in the basic sign-in flow described above, or only under additional configurations/scopes?
  2. Which component collects it: the embedded SDK, the Google-hosted sign-in experience, or another service?
  3. What examples, purposes, and conditions should an app developer use to determine the appropriate App Store App Privacy disclosure? Is it linked to the user, and is any such use considered tracking under Apple's definition?
  4. Is the manifest intentionally a superset of possible integrations? Is there updated official guidance mapping basic sign-in to the manifest categories?

We are preparing accurate privacy disclosures and want to avoid assuming either that an unused API means no collection, or that all declared SDK categories necessarily occur in our specific integration.

Related clarification: https://github.com/google/GoogleSignIn-iOS/issues/646#issuecomment-5974207621 explains the conservative phone-number declaration for version 8.0.0. Thank you for that explanation. Could you confirm how it applies to version 10.0.0 and provide the category-by-category clarification requested above, especially for DeviceID, OtherUsageData, and OtherDataTypes?

References:

Vorherrschende Sprache
Objective-C
Sterne
756
Forks
283
Ø Merge
3 T. 1 Std.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus google/GoogleSignIn-iOS

Alle Issues in google/GoogleSignIn-iOS

Ähnliche Issues

Weitere Issues zu Objective-C

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.