What happened?
facing issue to upload on ios TestFlight xcode version 16 macOS 15.0
xcrun bitcode_strip -r platforms/ios/YourApp/Plugins/YourFramework.framework/YourFramework -o platforms/ios/YourApp/Plugins/YourFramework.framework/YourFramework
already tried bitcode_strip command but also that didn't work.
The following issues occurred while distributing your application.
Asset validation failed
Invalid Executable. The executable '***** Syndrome.app/Frameworks/OneSignal.framework/ OneSignal' contains bitcode. (ID: fda6a528-a835-4b16-8252-893d8d16acbd)
Steps to reproduce?
create build , upload it on testflight and you'll get error
OneSignal Cordova SDK version
Release 3.3.1
Which platform(s) are affected?
iOS
General
RSS for tagDive into the vast array of tools and services available to developers.
Post
Replies
Boosts
Views
Activity
I've recently gotten an app published to the IOS store. I made this app using React Native and testing through Expo Go. In Expo, everything functioned OK, but, once downloaded fully on my IPhone, one of the functions isn't working. Specifically, it's an "Enter" button that stores calendar information (nothing more than a date, time, and event name) through the React AsyncStorage function. Is there something wrong with AsyncStorage? For more clarity, all other touchable opacities in the app function as intended.
We have a Push-To-Talk application, which also allow user's to share the PDF file documents.
On receiving a PDF file document, which has a space in its file name.
On saving the document in the DB with space. When user is trying to access the PDF file, in order to rule out issues where there can be special character's in its file name, we are encoding the file name using stringByAddingPercentEncodingWithAllowedCharacters, and URLPathAllowedCharacterSet is the character set used which converts space character (" ") to %20.
Later, path of the same encoded file name is sent to fileURLWithPath:.
When the encoded URL is passed to [NSFileManager fileExistsAtPath:] the file is not found in the since in DB, file is saved with a space, but in the URL %20 is been swapped in-place of space character.
Issue case: Here, on passing the same encoded URL path of the PDF file to [NSFileManager fileExistsAtPath:] is returning false;
Query: On passing the filename with spaces encoded with stringByAddingPercentEncodingWithAllowedCharacters to [NSFileManager fileExistsAtPath:], the path is not converted back to the decoded file name and returning false
We have used a work around on this case, by forming the URL of the PDF file without encoding and passing it to fileURLWithPath, issue is not seen here.
We have a query here, i.e. will fileURLWithPath will be able to handle different special characters without encoding.
We have also raised a Feedback Ticket on same: https://feedbackassistant.apple.com/feedback/16049504
Is there a way I can use the lldb user defined commands, which I can load from a KDK, to determine how much memory my kext has consumed? Is there a way to figure out what size blocks they are?
I have already run the showallclasses command and the output has assured me that I am not leaking any objects which are defined by my driver's classes.
Thanks,
Tim
Hi,
I run a service that protects API calls from Apple ecosystem apps with several layers of security, one of them being DeviceCheck's server-to-server functionality. All requests arrive with a DeviceCheck token that I send to Apple to validate.
Essentially I'm using the functionality listed here:
The server-to-server APIs also let you verify that the token you receive comes from your app on an Apple device.
https://developer.apple.com/documentation/devicecheck
However, occasionally I see huge bursts of traffic that contain valid DeviceCheck tokens from a scripter. I want to understand how they are generating them. It seems like they have identified a way to forge tokens.
Here are traffic patterns for my site. The scale of the y-axis is somewhat arbitrary due to how I'm sampling the requests, but you get the gist. You can see the dark green bars at the bottom are general traffic, and the light green is what we rejected (we have other layers besides DeviceCheck that reject traffic). Interestingly, though, all those light green requests contained valid device check tokens!
I have thousands of the tokens stored in a file for analysis.
Are there known ways that Apple knows of tokens being forged? I wanted to open a TSI for this but the flow requires an Xcode project, and there is no Xcode project to demonstrate this issue. I would really like to get in contact with someone from Apple that either works on DeviceCheck or supports it.
Hundreds of apps in the store depend on my service, and DeviceCheck forms a layer of security that I want to rely on. Obviously we can't solely rely on it, and we don't, but it does form an important layer of our defense. So I ask:
If you know of a way to forge tokens, please comment and I'll shoot you a DM
If you work at Apple and know who I can talk to, please help me work through the process to get in touch with them.
Thanks,
Lou
Hi,
We have few MacStudio servers that when we ssh as users to it and trying to run some commands fro /usr/bin, they staying in hang state for infinite.
When root user do the same commands are working properly
Example for hanging commands : clang, gcc, make, ld etc
Add as attachment the dtruss out for ld -v command to help debug it
Thanks,
Amir
dtruss out from ld -v command
Hey guys.
I’m working on a project where I’m using the SwiftTesting framework instead of XCTest to run my unit tests. I have a file (test.png) located in my test resources folder:
PackageName > Tests > PackageNameTests > Resources > test.png
I’m trying to access this file in my tests, but I’m running into issues when trying to load it dynamically. Here’s what I’ve tried so far:
Using Bundle.module.path(forResource:ofType:): This approach didn’t work, as Bundle.module seems to be unsupported or returns nil in Swift Testing.
Using #file Macro for Relative Paths: I tried constructing a path based on #file and navigating to the resources directory, but it also didn’t yield the correct path.
Has anyone successfully loaded test resources in the Swift Testing framework? Is there a recommended way to access resource files in Swift Testing, especially for projects where Bundle.module isn’t available?
I've gone through the Apple Docs for Swift Testing, but I can't seem to find anything that answers my question.
Thanks in advance guys!
Hello,
I am trying to read debug symbols from a binary obtained from simple "hello world" C code. I use default gcc (Clang) on macos15, then try to install gcc-14 with hombrew
$ gcc -g program.c -o program
then run
$ dsymutil program
I got :
warning: no debug symbols in executable (-arch arm64)
I am doing something wrong here. My final objective is to be able to use my binaries in total view for debugging. Without debugging symbols, I can debug properly .
Thank you
[Not sure if this is the best sub-forum - please move or suggest where I can move to a better forum if needed!]
I am supplying some .dylibs (Universal) to a client - they were build on macOS 13 (Ventura), using Xcode 14.2. macOS deployment target was set everywhere to macOS 10.11.
The client built their own wrapper app, and are successfully running it everywhere - except on an Intel Mac running macOS 11 (Big Sur). They get the error dialog at startup:
"demoapp" cannot be opened because it is from an unidentified developer.
However, it does work correctly (no 'unidentified developer' error) in macOS 12 (Monterey) and newer OS versions, both on Intel and ARM. I do not have that old of a Mac to test on. I also explained that macOS 11 is no longer supported by Apple, but they do need to support it for a little while longer.
I'm not sure what to suggest or have them check - or is this expected, and if so, why?
Can an Persional developer account develop, debug, and publish Network Extension apps?
Hi Team,
How can I share info beetween two differnt App. What king of approach should I use. Thanks in advance.
In my case I whant to share a token or an string like "GM-8090"
It was required to compile older WebKit versions for other operating systems and was made available up until ~2020 by Apple under the url http://developer.apple.com/opensource/internet/webkit_sptlib_agree.html
However this site and file does not seem to be available anymore. Looking for someone who can provide this file.
I'd like to put this on archive.org for historic purposes.
We have a service that was accessing the WeatherKit Api. We had the service up and running, using JWT authorisation and a registered service. Some time ago it stopped working, returning a 401 response. We need the service to be up again now.
We created a new JWS token following this instruction: https://dev.iachieved.it/iachievedit/weatherkit-rest-api/ which already workedfor us in 2022. However, we keep receiving a 401 error and the "reason": "NOT_ENABLED" message. We found that several other uses seem to be experiencing similar problems. We also created a new key and service identifier, but no luck.
I am using two iPhone11 devices, having iOS v17.6.1 for automation testing using Seleniumv4.X-Appium v2.x.
Today I updated the mac to Sequoia15 version which updated the XCode to v16.
Just after this update, I could not able to run the previously running automation script. The console message is "org.openqa.selenium.SessionNotCreatedException:
Could not start a new session. Response code 500. Message: Unable to launch WebDriverAgent. Original error: xcodebuild failed with code 70. This usually indicates an issue with the local Xcode setup or WebDriverAgent project configuration or the driver-to-platform version mismatch."
So I can see from the documentation that XCTAssertEqual(x, y) becomes #expect(x == y), but what about XCTAssertEqual(x, y, accuracy: 0.2)?
Does something already exist or do we need to write a more involved statement to see if x is less than y plus z and more than y minus z?
Hi,
I have a library for my iOS Apps. It uses among other things the Combine framework, Core Location and OSLog. I manage the library using the Swift Package Manager (SPM) and usually build via XCode, which works fine. However for CI I would like to build everything from the terminal. So I do call 'swift build' on the terminal. This produces errors such as:
'PassthroughSubject' is only available in macOS 10.15 or newer
'os_log(:dso:log::_:)' is only available in macOS 10.14 or newer
'eraseToAnyPublisher()' is only available in macOS 10.15 or newer
'authorizedWhenInUse' is unavailable in macOS
'AnyPublisher' is only available in macOS 10.15 or newer
'showsBackgroundLocationIndicator' is unavailable in macOS
...
These are all from the used frameworks. However, I do not care on which version of macOS, for example, PassthroughSubject is only available at, since the library is iOS only. Too make sure of that I added "platforms: [.iOS(.v14)]" to my Package.swift and thought this would be sufficient, so the project does not get build for macOS.
Can anyone please tell me or give me a hint on what I am getting wrong here?
Running
xcrun xcresulttool get build-results --path ResultFile
does not always show the warnings that the build emitted, If I run the legacy command,
xcrun xcresulttool get --legacy --path ResultFile
against the same file, there are (numerous) warnings, where the non-legacy call above shows no warnings.
Why is gnu++14 specified locally and gnu++20 specified in CI?
I have built an iOS app using flutter. The app (debug and release build) works fine on real devices. But when trying to run integration tests on this app using appium on an emulator, the app keepas crashing randomly with these error logs:
https://docs.google.com/document/d/1Z1f7hudmpHUATnFvoSZeAAoi8-NyVn6P9BFHNOZkzyA/edit?tab=t.0
Any help would be appreciated
I am working on adding Objective-C ABI support to DLang and currently I'm getting the following error when linking with ld.
Assertion failed: (fixups().size() == 1), function classTarget
I'm curious as to why I am getting this error, looking at the objective-c runtime source, i have not applied any of the fixup flags to any protocol definitions. From my understanding, the source of the linker is not available so it's a bit on the difficult side to determine which part is wrong.
The source of my pull-request is available here:
https://github.com/ldc-developers/ldc/pull/4777