Search results for

smb big sur

11,804 results found

Post

Replies

Boosts

Views

Activity

Can I fix this big difference between swiftui preview and actual watch widget layout?
Hi, working on customising my live activity Smart Stack layout for ios18. A thing that is very frustrating is that I consistently looks different for me in the Xcode preview and on the actual watch. See attached screenshots below. The sizes are different, and italic doesn't work on the watch, for example. It makes it time-consuming and unpredictable, so I was wondering if this is a known issue or if I'm doing something wrong, and also can I do anything? thanks edit: this is the layout: var body: some View { VStack(alignment: .center, spacing:4) { HStack(alignment: .center) { IconView(resource: n-compact-w, bgColor: Color.checkedIn, padding: 2, paddingRight: 6, paddingBottom: 6) .frame(maxWidth: 25, maxHeight: 25).aspectRatio(1, contentMode: .fit) Text(Checked Out) .font(.title3).bold() } Text(status.loc) .font(.headline) .multilineTextAlignment(.center) Text(FormatUtils.getFormattedDateTime(status.time)).font(.subheadline) .multilineTextAlignment(.center).italic() } }
4
0
583
Oct ’24
getattrlistbulk lists same files over and over on macOS 15 Sequoia
A customer of mine reported that since updating to macOS 15 they aren't able to use my app anymore, which performs a deep scan of selected folders by recursively calling getattrlistbulk. The problem is that the app apparently keeps scanning forever, with the number of scanned files linearly increasing to infinity. This happens for some folders on a SMB volume. The customer confirmed that they can reproduce the issue with a small sample app that I attach below. At first, I created a sample app that only scans the contents of the selected folder without recursively scanning the subcontents, but the issue didn't happen anymore, so it seems to be related to recursively calling getattrlistbulk. The output of the sample app on the customer's Mac is similar to this: start scan /Volumes/shares/Backup/Documents level 0 fileManagerCount 2847 continue scan /Volumes/shares/Backup/Documents new items 8, sum 8, errno 34 /Volumes/shares/Backup/Documents/A.doc /Volumes/shares/Backup/Documents/B.doc ... continue scan
18
0
1.1k
Oct ’24
Reply to DockKit tracking becomes erratic with increased zoom factor in iOS app
Be sure to pass in the camera intrinsics. Rather than compute them yourself, pull them from the AVCaptureDevice. I've seen something similar, when the zoom is at default, it's fine, as it increases, the fact that your view is zoomed in isn't known to the tracking system because incorrect intrinsics. So a small offset at low zoom because a big offset at bigger zoom and the system tells the accessory to rotate too much. Feedback loop.
Oct ’24
Production Issue - MetricKit is not generating daily metric payloads as expected since iOS 18
I'm a big fan of MetricKit. I decided to see how my apps are performing with iOS 18 and well, I'm not getting any metric payloads from those devices. Metric payloads received from my test devices adopting iOS 18 has pretty much bottomed out to zero. Is anyone getting MetricKit MXMetricPayloads from iOS 18 devices? FB15461298 - MetricKit: Production issue / regression with iOS 18 - Significant dropout or metric payloads being generated since 18.0 - nearly no reports To demonstrate the issue, I decided to graph the metric payloads my infrastructure receives for all of my apps across all of my devices over the last 16 months starting with WWDC23 timeframe. This data is grouped by count per month. A trend can easily be seen starting in June 2024 where I started to adopt iOS 18 betas. Zooming in since WWDC24, grouped by week, it is much easier to see the decline. Note, the second screenshot shows data collected from Xcode builds, TestFlight, and App Store. The last data point from today was a manual creat
2
0
825
Oct ’24
Issues with ProRAW MAX(48) and stock camera app
Hello developer community. I purchase recently my new iPhone 16 Pro Max; it is a premium device with great quality overall. However, I am having a big trouble shotting in ProRaw MAX (48 mode) with native camera. Just to be clear, the problem that i will describe do not happen in 3rd apps, such as ProCam; only with native camera. When I use ProRaw Max, and take the photo, and watch the photo in the gallery the image can’t load and render properly. Even, when I maximize the image to the maximum I can see pixelated portions, defects and super low resolution and excessive denoise. For comparison, this not occur with my previous iPhone 15 PM and/or when I capture photos from ProCam (same settings and configurations) in the 16PM. I proceed to take the photo, open the gallery and I see full of details, when zoomed to 100%. I tried to format the phone, reinstall the software via my mac. Tried even to look at some forums to find if there’s someone with the same issue, the information available so far is very
1
0
729
Oct ’24
Son note vocale IOS 18
Bonjour, Depuis la lise à jours vers IOS 18, j'ai un problème de son sur les notes vocales : le début de l'enregistrement est sur un son très bas, puis augmente progressivement. Que se passe-t-il ? C'est très gênant car je m'en sers beaucoup pour diverses raisons. Hello, Since updating to IOS 18, I have a sound problem on the voice notes : the beginning of the recording is on a very low sound, then gradually increases. What's the problem? It's very annoying because I use it a lot for various reasons.
1
0
147
Oct ’24
WidgetKit widgets vanish in Montery with Xcode 16
We have recently added WidgetKit widgets to an existing product, and they've been working great on Macs using Big Sur and later. Recently, when installing a build on a Montery Mac, the widgets were no longer in Notification Center. After some trial and error, we discovered that if we build the project with Xcode 15.4, the widgets appear, but if we build with Xcode 16, the widgets vanish. This seems to happen on Macs running Big Sur or Monterey. The project is being built on Macs running Sonoma (both Apple Silicon and Intel). Is there a build setting in Xcode 16 that may have this effect?
3
0
441
Oct ’24
Reply to NSDirectoryEnumerator returns nil
Also, the enumerator mechanism is kinda out old school. A better way to enumerate a directory is with the -contentsOfDirectoryAtURL:includingPropertiesForKeys:options:error: method. This has a couple of important advantages: The keys parameter lets you prepopulate the properties you need on each URL. This is really big performance boost if you’re working with a high-latency volume, like one mounted over the network. It gives you a useful error if it fails. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
Oct ’24
Reply to EACCES Error on binary included in Electron app
[quote='807772022, Dreculah, /thread/765576?answerId=807772022#807772022, /profile/Dreculah'] As an alternative, might I have a script that installs this sox binary to /opt/bin/sox? [/quote] Yes, as long as your app isn’t sandboxed. If it is sandboxed, using a location like this is trickier. Oh, and binaries like this usually go into /usr/local on macOS. See the not-very-well-known hier man page. You can put it into /usr/local/bin directly, or create your own product directory and put it into /usr/local/my-product-name/bin. But, yeah, the big drawback with this approach is that you can run into conflicts, where the user has the wrong version of the tool installed. That’s one of the advantages of embedding helper tools into your app. Coming back to the big picture, if you were using Xcode then I’d be able offer more help. As I mentioned before, we have a specific doc that covers the sandboxed case, Embedding a command-line tool in a sandboxed app, and your non-sandboxed case is significantly
Topic: Code Signing SubTopic: General Tags:
Oct ’24
CarPlay issues
I am also currently having the same issue after updating to IOS18 And iPhone 16pro max Whether wired or wireless sound quality is poof and very mono. At some point it corrects itself then you touch the phone screen then back to mono again. Making phone calls big issue. Nothing respond,nothing else resolve it. My Bluetooth works fine. Please fix this… so tired of this
1
0
479
Oct ’24
Reply to Problème de son Bêta IOS 18 Version 2
Je post ici car nul part ailleurs on parle de ce problème. Alors quand version final le problème de gestion du son existe toujours. ici, pour moi, j’ai un problème de categorisation du son. En effet ma musique sort comme un appel que sur le haut-parleur du haut. En Carplay que sur les enceintes avant, comme un appel ou le GPS. Autre problème les alarmes urgente ne sonnent plus si le téléphone est en mode vibreur, embêtant pour les app de réveil… effectivement le fait de passer un appel régle temporairement le problème !
Oct ’24
Core Data transformable vs relationship
I'm working on an app that is using Core Data. I have a custom big number class that boils down to a double and an integer, plus math functions. I've been using transformable types to store these big numbers, but its forcing me to do a lot of ugly casts since the number class is used throughout the application. I figure I can either have my stored values be named differently (e.g. prefix with underscore) and have a computed variable to cast it to the correct type, or find some way to move the big number class to being an NSManagedObject. The issue with this is that the inverse relationships would be massive for the big number class, since multiple entities use the class in multiple properties already. Would it be recommended that I just keep using Transformable types and casts to handle this, or is there some standard way to handle a case like this in Core Data relationships?
0
0
326
Oct ’24