Post not yet marked as solved
It is most likely caused by:
renderer.lineWidth = 0.7
Try...
renderer.lineWidth = 1
...and see if that fixes it.
Post not yet marked as solved
In the Preview, you need to pass a "scannedCode" to your "PageThree" struct.
Try this:
struct PageThree_Previews: PreviewProvider {
static var previews: some View {
PageThree(scannedCode: "some text...")
}
}
Post not yet marked as solved
Instead of:
let mylocation = String(location)
Try:
let mylocation = String("\(location.x),\(location.y)")
From the Xcode 14 Beta Release Notes
Xcode 14 beta requires a Mac running macOS Monterey 12.4 or later.
Some features require Apple silicon, but Xcode 14 itself does not.
Try something like this, to get started:
struct TabScreen: View {
var body: some View {
TabView() {
Text("HomeScreen")
.tabItem {
Image(systemName: "house")
Text("Home")
}
Text("NotificationsScreen")
.tabItem {
Image(systemName: "bell")
Text("Notifications")
}
Text("ExploreScreen")
.tabItem {
Image(systemName: "binoculars")
Text("Explore")
}
Text("ProfileScreen")
.tabItem {
Image(systemName: "person")
Text("Profile")
}
}
}
}
Post not yet marked as solved
On App Store Connect, under Users and Access:
Having set the "Role" for a developer, you can set the "Apps" that they have access to.
This can be:
All Apps
or one or more specific apps (which you can choose from a drop-down list)
Of course, the Apple account itself, and the Account Holder role, should be under your control.
For the "Developer" role, you may need to add additional permissions such as "Access to Certificates, Identifiers and Profiles", depending on how you manage the app.
A full list of permissions for each role is shown, on tapping the role.
It looks like having both axes in your ScrollView is forcing the content to the center.
Removing .horizontal sends it to the top.
So as a possible fix (here's a minimal example), try:
var body: some View {
ScrollView(.horizontal, showsIndicators: true) {
ScrollView(.vertical, showsIndicators: true) {
ZStack {
Text("content appears at top")
}
}
}
}
Post not yet marked as solved
Should it be Memo1.string.length - 1 ?
Post not yet marked as solved
You are talking about NOT
With a Swift Bool, you can use toggle()
DateFormatter is now threadsafe, but creating one is quite expensive.
You certainly shouldn't be creating one every time you call logToFile!
So you might try using an extension, like this:
extension DateFormatter {
static let myFormatter: DateFormatter = {
let formatter = DateFormatter()
formatter.dateFormat = "yyyy-MM-dd'T'HH:mm:ss.SSS"
formatter.timeZone = TimeZone(secondsFromGMT: TimeZone.current.secondsFromGMT())
formatter.locale = Locale(identifier: "en_US_POSIX")
return formatter
}()
}
(Give it a more meaningful name, of course)
Then in your logToFile, you can use it like this:
let localDate = DateFormatter.myFormatter.string(from: Date())
This will be more efficient, and should fix your issue.
Post marked as Apple Recommended
It's Betas all the way down.
Ventura > Xcode 14 > iOS 16
Post not yet marked as solved
The future does not look good for Intel Macs, Looking at the rate they are being dropped from macOS Ventura support.
Some Ventura features are also exclusive to Apple Silicon Macs.
The line:
public func storeFaveArtwork(artwork) {
does not make sense.
I would expect something like:
public func storeFaveArtwork(artwork: Artwork) {
