dsym file

I am curious as to know if i calculate the checksum of an ipa file and upload the same to app store, and then after installing the app on my device, if i extract the ipa file and compare the checksum will it match? or will it vary from device to device, because of bitcode and app thinning slicing? Some banks have been showing ipa file checksums on their websites, and even inside their apps and showing messages like checksum matches! i was just curious as to know how would one go about validating this!? Or is this even possible, what about the checksum of the executable at runtime? Can we check this? will it match?

Hello everyone, Our app was recently rejected under Guideline 5.0 – Legal (U.S. Sanctions Compliance). Apple review reported that the binary contains the following domain: https://lib.eshia.ir However, after extensive investigation: • The app does NOT connect to this domain • The app does NOT provide services to sanctioned regions • The domain does NOT exist in our source code, API calls, or UI • Network logs confirm no outgoing requests to this host We suspect the reference is coming from a bundled third-party dependency dataset (possibly a public suffix / domain validation / fraud detection list embedded in a framework). We already: Extracted IPA Scanned all source files Ran strings on the main binary Checked networking layer But we still cannot identify which framework contains this entry. Questions: Has anyone faced a sanctions rejection due to a domain inside a compiled SDK dataset? Is Apple expecting removal of the exact string from the binary even if unused? How do you typically identify the s

When I enter webp image to the assets catalog I get warrning: /Users/..../Assets.xcassets The image set Card-Back references a file Card-Back.webp, but that file does not have a valid extension. It works, I see all my images perfect. How can I fix the 200+ warrnings?

Hello, according to pkware, the latest zip standard is 6.3.10, what standard does ios 26 use to make zip files in the files app ?

When building in Xcode on MacOS Tahoe, it seems it is no longer possible to dynamically specify a small size toolbar for NSToolbar/NSToolbarItem. It works in MacOS code compiled and linked on earlier systems. I don't want to use SFSymbol, or templates. I have over 60 custom-made .png toolbars, in individual Image Set files, at the previous requisite sizes of 24x24 / 48x48, and 32x32 / 64x64. Sure -- I can configure an NSToolbar with whatever size .png assets I want. I just can't dynamically switch between the two groups of sizes. According to the Apple Coding Assistant, the only solution is to change the image names of each of the NSToolbarItems at runtime. OK -- but even when attempting that, the NSToolbarItems refuse to take on their smaller size... ...unless: they are attached to a custom view NSToolbarItem with an NSButton of style Bevel. I have about 10 of those, and YES -- I CAN change those to a small size. Is this REALLY what I'm forced to do?! The Apple Coding Assistant just runs me around i