IL2CPP stripping still breaks NSData and other wrappers: the packages' link.xml files are ignored and most constructors lack [Preserve]
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 55/100
Rechercherichtung
Start by tracing InteropReference.PointerCast<T> to ReflectionUtility.CreateInstanceOrDefault and inspect the (IntPtr) constructors listed for Apple.Core and Apple.GameKit. Check how Unity discovers package link.xml files through IUnityLinkerProcessor.GenerateAdditionalLinkXmlFile, then reproduce with the stated iOS IL2CPP setup at Managed Stripping Level Low. Done means every wrapper reachable through PointerCast survives stripping without an app supplied link.xml.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Describe the bug
Wrapper objects are created through reflection (InteropReference.PointerCast<T> calls ReflectionUtility.CreateInstanceOrDefault, which looks up the (IntPtr) constructor). Nothing calls those constructors directly, so IL2CPP managed stripping (Low and up) removes them, and the fallback Activator.CreateInstance throws MissingMethodException: Default constructor not found for type ....
Each package ships a link.xml with preserve="all", but in our builds Unity never passes those files to UnityLinker. In our Unity 6000.6.4f1 player builds, the link.xml files it uses are the ones under Assets/ and the ones packages generate through IUnityLinkerProcessor (for example Library/com.unity.services.core/link.xml). The files inside com.apple.unityplugin.core and com.apple.unityplugin.gamekit are not among them, and neither is the one inside com.unity.nuget.newtonsoft-json.
Only 14 constructors have [Preserve] today, all in GameKit, most added by #73 for #61. These 35 don't (main, 96e4a04):
- Apple.Core: NSObject, NSData, NSString, NSError, NSException, NSNumber, NSNull, NSArray, NSArray, NSArrayInt64, NSArrayBoolean, NSArrayString, NSMutableArray, NSDictionary<TKey, TValue>, NSDictionary, NSDateComponents, Currency
- Apple.GameKit: GKLeaderboard, GKLeaderboard.Entry, GKLeaderboardScore, GKLeaderboardSet, GKScoreChallenge, GKInvite, GKMatch, GKMatchDelegate, GKMatchedPlayers, GKMatchmakerViewController, GKMatchmakerViewControllerDelegate, GKTurnBasedExchange, GKTurnBasedExchangeReply, GKTurnBasedMatch, GKTurnBasedMatchmakerViewController, GKTurnBasedMatchmakerViewControllerDelegate, GKTurnBasedParticipant, GKVoiceChat
NSData is the one most apps will hit: GKLocalPlayer.FetchItemsForIdentityVerificationSignature() builds its signature and salt with PointerCast<NSData>, so Game Center identity verification (used for server-side sign-in) fails. #54 tried to fix exactly that and was closed because #73 was expected to cover it, but #73 only changed GameKit. #128 hit the same NSData MissingMethodException in October and was closed after the reporter switched to Minimal stripping.
To Reproduce
- iOS project with Apple.Core and Apple.GameKit, IL2CPP, Managed Stripping Level Low, no link.xml of your own.
- Sign in to Game Center and call
GKLocalPlayer.Local.FetchItemsForIdentityVerificationSignature(). - MissingMethodException for
Apple.Core.Runtime.NSData.
Expected behavior
Every wrapper reachable through PointerCast survives stripping without each project adding its own link.xml.
Environment
Unity 6000.6.4f1, iOS, IL2CPP, Managed Stripping Level Low. Apple.Core 3.3.0 / Apple.GameKit 4.1.0 (27.0, ffe6174); also checked main (96e4a04). We haven't re-run this on 4.1.0 because our own link.xml prevents it; the NSData failure is the one #128 reports.
Additional context
Either register the shipped link.xml through IUnityLinkerProcessor.GenerateAdditionalLinkXmlFile (the way com.unity.services.core does), or put [Preserve] on every (IntPtr) constructor. Our workaround is a link.xml under Assets:
<linker>
<assembly fullname="Apple.Core" ignoreIfMissing="1" preserve="all" />
<assembly fullname="Apple.GameKit" ignoreIfMissing="1" preserve="all" />
</linker>
- Vorherrschende Sprache
- C#
- Sterne
- 1k
- Forks
- 257
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus apple/unityplugins
-
bug Plugin-in - Core
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 55/100
apple/unityplugins#132 ·
-
bug Plugin-in - Core
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 65/100
apple/unityplugins#131 · 1 zugewiesene Person ·
-
bug Plugin-in - Core
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 55/100
apple/unityplugins#125 · 2 Kommentare ·
-
Crash Issue On macOS 27 With Game KitEvtl. vergeben @ryzngard hat das vor 40 Tagen übernommen. Offenbug Plug-in - GameKit
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
apple/unityplugins#124 · 1 zugewiesene Person ·
-
Arguments for Push Message localisation in SendExchange do not seem to workEvtl. wieder frei @ryzngard hat das vor 169 Tagen übernommen, und es ist kein Pull Request offen. Offenbug Plug-in - GameKit
apple/unityplugins#98 · 2 Kommentare · 1 zugewiesene Person ·
Alle Issues in apple/unityplugins
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
Maintainer antworten meist innerhalb von 1 Tag
-
area-ai untriaged
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
dotnet/extensions#7956 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug needs-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 67/100
microsoft/microsoft-ui-reactor#1567 ·
Maintainer antworten meist innerhalb von 1 Tag
-
priority:p2
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
QuantConnect/Lean#10191 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
openclaw/openclaw-windows-node#2287 · 2 Kommentare · 1 Reaktion ·
Maintainer antworten meist innerhalb von 1 Tag