Post not yet marked as solved
My app was recently approved and I have been trying to watch metrics so I an adjust my marketing campaign. When I go to the Apple Developer analytics dashboard there isn't anything there and its been almost a week since releasing my pre-order. The only message I see is "Not enough Data: Data is displayed when a certain number of data points become available."
When will this data become available and how many data points are needed until I can begin tracking? On the Google Play Console I was able to see when I had as little as 2 pre-registered users.
Post marked as Apple Recommended
Hi guys,
I am migrating my widgets to iOS 17 and because I already manage my layout margins, I just want to disable to new built-in widget content margins.
I did it by using ".contentMarginsDisabled()" on the WidgetConfiguration and it works fine at run time.
WIDGET CODE
struct MyWidget: Widget {
let kind: String = "MyWidget"
var body: some WidgetConfiguration {
return IntentConfiguration(kind: kind, intent: MyWidgetIntent.self, provider: WidgetProvider<MyWidgetIntent>()) { entry in
WidgetView<MyWidgetIntent>(entry: entry)
}
.configurationDisplayName("My Widget")
.supportedFamilies([WidgetFamily.systemMedium])
.contentMarginsDisabled() // <-- HERE
}
}
RESULT
Nevertheless, when previewing the WidgetView in a WidgetPreviewContext I didn't find anyway to disable the content margins (because manipulating directly the view and not a WidgetConfiguration).
PREVIEW CODE
struct MyWidget_Previews: PreviewProvider {
static var previews: some View {
WidgetView<MyWidgetIntent>(entry: WidgetEntry<MyWidgetIntent>())
// .padding(-16) Need to add this negative padding to disable margin
.previewContext(
WidgetPreviewContext(family: .systemMedium))
}
}
Do you know how to disable the content margins for widget preview?
I am playing around with Live Activities and got everything working on the iOS 16.1 beta 2 simulator using Xcode 14.1 beta 2 (14B5024i).
However, running the same code on a real physical device (iPhone X) running iOS 16.1 beta 2 does not show the Live Activity on the lock screen at all. 😵
Did anyone get their Live Activity working on a real device yet, or is this an issue with the current beta?
Things I have already checked:
ActivityAuthorizationInfo().areActivitiesEnabled returns true on my physical device
let activity = try Activity.request(...) successfully completes without throwing and I can see the activity.id printed to the console
Other live activities - such as the iOS system timer activity - do show up on my physical device just fine
Post not yet marked as solved
Has anyone else experienced issues with Spotlight losing indexing of the Applications?
Spotlight no longer displays any applications in the results when typing in an application name.
Additionally it appears to be ignoring the settings of "Spotlight" set within the preferences. Example: I have "Websites" & "Siri Suggestions" turned off, however these still appear in the search results of spotlight.
Post not yet marked as solved
I'm not sure if I'm changed an unknown-to-me setting somewhere, but since this morning, after profiling an app (metal, allocations, etc), every project I run/build on Xcode 15b3, either on simulator or on device, displays partially-alpha images blended to black, as if there was some problem in the process of compiling the PNGs (lack of premultiplying, color space, etc).
If I open those same projects on Xcode 14, they are displayed everything as they should.
Also, If I open them on other computers with Xcode 15b3 other than mine, it also works fine. And it was working fine for me this morning as well, but not anymore.
I've tried uninstalling Xcode beta and the simulator a few times, cleaning folders and preferences, hoping it was some setting I changed by mistake with some hotkey, but no luck so far.
I'll attach two pictures, one from Xcode 14, and the other one from Xcode 15b3, hoping it's some silly thing I'm missing.
xc15b3:
xc14:
I have an app in the app store which is working fine. Some users reported that they have app crashing when they are using iOS 17.4 beta. I could recreate the issue and it is happening when ModelContainer is crerated. This code..
do {
let configuration = ModelConfiguration(for: MyTodo.self, isStoredInMemoryOnly: false)
modelContainer = try ModelContainer(for: MyTodo.self, configurations: configuration)
} catch {
fatalError("Failed to load model container.\(error)")
}
is throwing this error message:
Fatal error: Failed to load model container.SwiftDataError(_error: SwiftData.SwiftDataError._Error.loadIssueModelContainer)
Post not yet marked as solved
I have got an error response when I have summit app for review. Any one face this issue please kindly help. Thank
{
"errors": [
{
"id": "a9580e9f-103a-4a02-94c0-0a181df057df",
"status": "422",
"code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING",
"title": "Beta contract is missing for the app.",
"detail": "Beta Contract is missing."
}
]
}
Post not yet marked as solved
I am trying to release a beta version of an app for internal TestFlight testing but I keep getting a notification saying it has invalid binary. I have tried looking this up but I can't find anything that helps. Please help! If you need anything in addition to this, let me know. I just wasn't sure what to share.
Post not yet marked as solved
When I upgraded the system to iOS 17.4 Beta, the AppEnum in my code became invalid. I selected an AppEnum option on the desktop widget, but the widget did not synchronize.
Post not yet marked as solved
When showing PDF document in UIDocumentInteractionController and when tap on share button > Print, app crash.
Below is the crash log
*** Terminating app due to uncaught exception 'UIApplicationInvalidInterfaceOrientation', reason: 'Supported orientations has no common orientation with the application, and [UIPrintPanelNavigationController shouldAutorotate] is returning YES'
It's a iPad app supporting Landscape orientation only. And its in Objective C.
Post not yet marked as solved
FeedbackID: FB13636921
I'm using /usr/sbin/screencapture -v -x -C -k -R 0,0,500,500 /path/to/a/movfile/in/a/folder/in/my/apps/sandbox/Group/Container in my app to allow users to capture screenshots and recordings.
Screenshots keep working fine on macOS Sonoma 14.4b23E5196e, but video recordings no longer work.
I'm guessing the following log output has something to do with it:
default 15:01:53.151819+0100 screencapture sampleBuffer: start recording time: 3123.604833 target: 3123.474266, overshot: 0.130568
error 15:01:53.185179+0100 screencapture <private>:246:<private> Not writable url (null).!folderIsWritable == true
error 15:01:53.185236+0100 screencapture <private>:50:<private> We could not create a byte stream!
error 15:01:53.185252+0100 screencapture <private>:87:<private> NULL byte stream.
error 15:01:53.185298+0100 screencapture <private>:3479:<private> ### Err -45,
error 15:01:53.185312+0100 screencapture <private>:3814:<private> ### Err -45,
error 15:01:53.185334+0100 screencapture <<<< AVCaptureMovieFileOutput >>>> Fig assert: "status == 0 " at (AVCaptureMovieFileOutput.m:2522) - CMIOFileWritingControlTokenStartWriting (err=-45)
error 15:01:53.185374+0100 screencapture <private>:1885:<private> ### Err -67452,
error 15:01:53.185388+0100 screencapture <private>:303:<private> FigMovieFormatFileWriter::PostProcessMovie: WriteMovie() errored!!! -67452
error 15:01:53.185476+0100 screencapture <private>:4687:<private> consolidate movie fragments err : -17913
default 15:01:53.185610+0100 screencapture <<<< AVError >>>> AVLocalizedErrorWithUnderlyingOSStatus: Returning error (AVFoundationErrorDomain / -11800) status (-45)
default 15:01:53.186201+0100 screencapture didFinishRecording: No trim finish. duration: 0.000000s size: 0, error: Error Domain=AVFoundationErrorDomain Code=-11800 "The operation could not be completed" UserInfo={AVErrorRecordingSuccessfullyFinishedKey=false, NSLocalizedDescription=The operation could not be completed, NSLocalizedFailureReason=An unknown error occurred (-45), NSURL=file:///Users/eternalstorms/Library/Group%20Containers/group.com.apple.screencapture/ScreenRecordings/3ED15EE7-A814-47A7-A398-29D5A6AD03C1.mov, NSUnderlyingError=0x6000031d80c0 {Error Domain=NSOSStatusErrorDomain Code=-45 "fLckdErr: file is locked"}}
error 15:01:53.186290+0100 screencapture recording failed. The operation could not be completed
Are there new entitlements we need for this in our apps starting with macOS Sonoma 14.4? Or is it a bug? Calling it directly from Terminal works.
Thank you,
Matthias
Post not yet marked as solved
In my Xcode 15 beta 8 setup, I'm encountering an issue with the iOS 17 simulator where StoreKit.Product.purchase() consistently throws StoreKit Error.Unknown while running XCTest.
Inside XCTest, I have declared SKTestSession(configuration: "").
I'm using try await StoreKit.Product.purchase(options: []).
However, it always throws StoreKit Error.Unknown. There's no such problem with the iOS 16.4 simulator, where I can retrieve the result and handle it appropriately. This issue is only present in the iOS 17 simulator.
Is there any necessary workaround or fix for this?
I've also included the console log output for your reference:
デフォルト 10:06:45.981812+0900 storekitd AMSURLRequest: [597e_SK2] Failed to fetch client ID domains from bag. Defaulting to not including analytics cookies. error = { Error domain=AMSErrorDomain, code=204 | URL = http://localhost:XXXXX/inApps/history?REDACTED
We're seeing server trust failures with iOS 17 that we don't see with iOS 16, particularly in debugging, when we build with Xcode 15. We handle
func urlSession(_ session: URLSession,
didReceive challenge: URLAuthenticationChallenge,
completionHandler: @escaping (URLSession.AuthChallengeDisposition, URLCredential?) -> Void)
and choose to deal with recoverable server trust failures of particular kinds ourselves. After our checks we end up calling the completion handler:
let credential = URLCredential(trust: serverTrust)
completionHandler(.useCredential, credential)
And everything continues.
This is working on macOS Venture and earlier and iOS 16 and earlier. It also works if we install our current release build on iOS 17. If we build with Xcode 15 and test on iOS 17 then calling the completion handler with .useCredential ends up failing with a -1200 error, and a message about a recoverable trust failure.
Has anyone else seen this behavior? Does anyone know if this is related to just Xcode 15, or to Xcode 15 + an interaction with iOS 17? Maybe the SDKs used with Xcode 15 are being stricter? In any case it would seem that saying .useCredential should cause it to .use the credential...
Post not yet marked as solved
I made the app file in xcode validate the app and then I shared it only in test fligth when I wanted to test it on my iphone 14 Plus device the following message appears try uploading other builds same thing happens with the other two apps
I've been two weeks trying to solve this bug or problem, I searched for information on google but what appears is from 2014 how much appstore had the name of itunes Connect, I have asked in other forums and ddicen to wait a while that is normal but I think it takes a long time.
If someone has gone through this and put you solve agadeceria you can help me
Post not yet marked as solved
Got a little app I am trying to build before launch, I've never built a watch only app, and it requires iOS 17 so I'm a bit stuck. When creating a watch only target, it seems that the template is broken. According to this: https://developer.apple.com/documentation/watchos-apps/creating-independent-watchos-apps/
There should be a blank iOS app target, that contains the watch app. The problem is once I go to build and upload the app to test flight, I get a bundle that Xcode has no clue what to do with (Because it only contains the watchkit app, and no containing xcode app.)
I'm guessing my only hope might be to create a watch only app targetted at iOS 9 with Xcode 14, then migrating to Xcode 15? I'm trying that now, but I guess I have another radar to file unless I'm missing something.
Post not yet marked as solved
Since going in the beta I have had problems uploading images to a WordPress site. This occurs with Safari and Chrome. There is no issue using my iPhone to upload to the same WordPress site and the support team at the hosting service have no issues uploading the same images I fail with using Windows systems. It is not consistent. The same file that has uploaded can later fail to upload after one or more files have failed to upload.
Very small images (5-20k) usually upload but larger than that and I start to get fails. When uploading to a different WP site I get uploads succeeding but the images are corrupt. But here aI also gett no issues using my iPhone uploading to the same site.
Post not yet marked as solved
Hi everyone,
I seem to have a serious problem with slow data download speeds on iPhone 12 Pro.
I've updated to latest iOS 17.4 beta - but still have same problem.
The beta is also on other iPhone SE v2, but it's not a problem.
How do i revert iPhone 12 Pro beta back to non beta version - ideally iOS 17.3.1?
Appreciate any help - thanks.
Post not yet marked as solved
Hi everyone
I started to see crash in iOS 17 beta 8 when try to show UIPrintInteractionController
for iOS 16 and less it works fine
let vc = UIPrintInteractionController.shared
vc.printingItem = pdfFileUrl
vc.present(animated: true) { (controller, success, error) in }
UIApplicationInvalidInterfaceOrientation', reason: 'Supported orientations has no common orientation with the application, and [UIPrintPanelNavigationController shouldAutorotate] is returning YES
App supported only portrait orientation
in AppDelegate
func application(_ application: UIApplication, supportedInterfaceOrientationsFor window: UIWindow?) -> UIInterfaceOrientationMask {
return .portrait
}
Post not yet marked as solved
Anyone know how to set Side By Side Comparison in the new commit UI? New UI seems to missing a lot of features like multi-select of files to discard/stage...
Post not yet marked as solved
In our mac catalyst app we access AppKit api's by using MacOS bundle(plugin).
when using CGDisplayCreateImage(_: CGDirectDisplayID, rect: CGRect) method the plugin crashes.
Implementation:
@objc
func windowMoved(_ notification: NSNotification) {
guard let win = self.window else {
return
}
let displayId = CGMainDisplayID()
let winRect = win.contentView?.convert(qrRect, from: self)
var rect = win.convertToScreen(winRect ?? self.bounds)
if let screenFrame = NSScreen.main?.visibleFrame {
rect.origin.y = screenFrame.height - rect.maxY
rect.origin.y += screenFrame.minY + win.titlebarHeight
}
guard let image = CGDisplayCreateImage(
displayId,
rect: rect) else {
return
}
guard let qrString = image.detectQRCode().first else { return }
// ...
}
Crash report in printed in console:
-[RPDaemonProxy proxyCoreGraphicsWithMethodType:config:machPort:completionHandler:]: unrecognized selector sent to instance 0x600000500960
(
0 CoreFoundation 0x00000001931deccc __exceptionPreprocess + 176
1 libobjc.A.dylib 0x0000000192cc6788 objc_exception_throw + 60
2 CoreFoundation 0x000000019329102c -[NSObject(NSObject) __retain_OA] + 0
3 CoreFoundation 0x0000000193148a80 ___forwarding___ + 976
4 CoreFoundation 0x00000001931485f0 _CF_forwarding_prep_0 + 96
5 ScreenCaptureKit 0x0000000227d9d95c SLSHWCaptureDesktopProxying + 692
6 SkyLight 0x0000000198b370a8 SLSHWCaptureDesktop + 488
7 SkyLight 0x0000000198b3b1ac SLSDisplayCreateImage + 252
8 MacPlugin 0x0000000112e0d374 $s9MacPlugin14MZMacQrScannerC11windowMovedyySo14NSNotificationCF + 1500
9 MacPlugin 0x0000000112e0d714 $s9MacPlugin14MZMacQrScannerC11windowMovedyySo14NSNotificationCFTo + 52
10 CoreFoundation 0x000000019315eb1c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148
11 CoreFoundation 0x00000001931f2db8 ___CFXRegistrationPost_block_invoke + 88
12 CoreFoundation 0x00000001931f2d00 _CFXRegistrationPost + 440
13 CoreFoundation 0x000000019312d648 _CFXNotificationPost + 768
14 Foundation 0x0000000194249434 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88
15 AppKit 0x00000001969ffbfc -[NSWindow _setFrameCommon:display:fromServer:] + 2056
16 AppKit 0x0000000197475080 -[NSWindow _windowMovedToRect:dueToMoveEvent:] + 184
17 AppKit 0x0000000196ae8630 -[NSWindow _windowMoved:] + 832
18 AppKit 0x0000000196ae82a4 -[NSWindow _internalHandleAppKitDefinedEvent:] + 152
19 AppKit 0x0000000196ae8074 -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 528
20 AppKit 0x0000000196ae7c90 -[NSWindow(NSEventRouting) sendEvent:] + 284
21 AppKit 0x00000001971adda8 -[NSApplication(NSEventRouting) sendEvent:] + 1800
22 UIKitMacHelper 0x00000001acb964f8 -[NSApplication(UINSApplicationSwizzling) _uinsSwizzledSendEvent:] + 252
23 AppKit 0x0000000196dfb954 -[NSApplication _handleEvent:] + 60
24 AppKit 0x00000001969afd24 -[NSApplication run] + 512
25 AppKit 0x0000000196986fa4 NSApplicationMain + 880
26 AppKit 0x0000000196bd9798 +[NSWindow _savedFrameFromString:] + 0
27 UIKitMacHelper 0x00000001acb82198 UINSApplicationMain + 972
28 UIKitCore 0x00000001c2ea2924 UIApplicationMain + 148
29 MyApp-DEBUG 0x00000001049d2d04 main + 64
30 dyld 0x0000000192d020e0 start + 2360
This is working fine in all previous version but crashing in macOS beta 14.4 and 14.4.1.