tikhop / asn1swift Goto Github PK

Hi,

Using latest TPInAppReceipt in shared code in WatchOS and iOS. I have some crash reports coming in from WatchOS only (code identical to iOS). Unfortunately symbolication fails for some reason (I import TPInAppReceipt as a swift package manager module, and i think there's a bitcode related bug here). So the obfuscated trace looks like this:

0 - 0x000c70b6 hidden#590 + 40 (_hidden#69:0)
1 - 0x000c73ca _hidden#93 + 22 (_hidden#69:0)
2 - 0x000c73ca hidden#592 + 38
3 libswiftCore.dylib 0x6dc1af14 dispatch thunk of Decodable.init(from:) + 12
4 - 0x000e55e6 hidden#222 + 774 (_hidden#643:1575)
5 - 0x000df70a _hidden#772 + 32 (_hidden#643:1547)
6 - 0x000df70a ASN1Decoder.decode(_:from:template:) + 340 (_hidden#643:46)
7 - 0x000d99b6 hidden#2010 + 138 (_hidden#2074:63)
8 - 0x000d1250 InAppReceipt.init(receiptData:rootCertPath:) + 34 (_hidden#69:0)

I appreciate this is not very useful, but just wanted to start a discussion in case someone else is aware of this.

Thanks again!

When using ASN1Swift in Xcode 12, as a SPM Package, I get this warning during build:

the target name ASN1Swift has different case on the filesystem and the Package.swift manifest file

Unhelpfully, it doesn't point out which exact file is the problem; and Git famously does not accommodate MacOS' case-insensitive filesystem all that well (it makes it difficult to commit a filename case change, since the file name is the "same" in mac world.)

This is minor, since the package still works fine; but: is it possible that some file has correct case on your development machine's filesystem, but got into Git with the wrong case somehow?

I'm trying to extract the R and S values (as Data) from a Data stream. Is that possible with this project? Thanks

the word read should read real in this line.

this name (CetrificatesContaner) is misspelled.

Privacy Updates for AppStore submission

Expected Behavior

Developers are responsible for all code included in their apps. At WWDC23, Apple introduced new privacy manifests and signatures for commonly used third-party SDKs and announced that developers will need to declare approved reasons for using a set of APIs in their app’s privacy manifest.

Current Behavior

The library doesn't provide Privacy Manifest file

Possible Solution

The library should provide Privacy Manifest if it collects information or access "Required Reasons API"

Additional Info

When including this package in an Xcode project, I get the following warning during the Resolve Package Graph build step:

the target name ASN1Swift has different case on the filesystem and the Package.swift manifest file

It looks the target folder in the filesystem is asn1swift when it should be ASN1Swift.