wait.. adding to PLIST or Entitlements?I added to plist and seems to work, but docs state we must add to entitlements...
ingconti
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
so the way is plist, not entitlements....
a bit late, but hpe can help1) ln ..does not work any more in Catalina2) mysql lib are newer.. with less bugs but as always bad....so ...https://stackoverflow.com/questions/17465902/use-of-external-c-headers-in-objective-c/60130956#60130956
OSX catalina: dialog.isAccessoryViewDisclosed = true
I read in late, but I can say1) set to Yes if You are going on Apple Store(read here soem idea.. https://www.infoq.com/articles/ios-9-bitcode/ )2) I used it in enterprise dev, too: For final user is he same.(for quick enterrpise dev. for example is fster to leave it off, but is mainsly to save exporting time..)
a bit in late.. but for next people...
I do calc let index = col + row * self.MaxCols outside, otherwise I got your message.
let gr = GeometryReader { (geometry : GeometryProxy) in
VStack() {
ForEach(0..<self.MaxRows) { (row: Int) in
HStack {
ForEach(0..<self.MaxCols) { (col: Int) -> GridCellView in
let index = col + row * self.MaxCols
return GridCellView(
w: (geometry.size.width / CGFloat(self.MaxCols)) - 25, // compensate inset..
titleAndText: firstLevelQuestions[index],
room: self.room,
troubleShootings: troubleShootings[index] )
}
}
}
}
my 2 cents for swift:
// swift implementation of ADC call
let NATIVE_EXECUTION = Int32(0)
let EMULATED_EXECUTION = Int32(1)
let UNKONWN_EXECUTION = -Int32(1)
func processIsTranslated() ->Int32 {
var ret = Int32(0)
var size = ret.byteWidth
	 let result = sysctlbyname("sysctl.proc_translated", &ret, &size, nil, 0)
if result == -1 {
if (errno == ENOENT){
return 0
}
return -1
}
return ret
}
func processIsTranslatedStr() -> String {
switch processIsTranslated() {
case NATIVE_EXECUTION:
return "native"
case EMULATED_EXECUTION:
return "rosetta"
default:
return "unkown"
}
}
```
Swift see at:
https://developer.apple.com/forums/thread/652667?answerId=618217022&page=1#622923022
Apart form very good Apple materials, I onesti think without a serious CS college course. the task is vey hard: too many concepts You can only undestand after a graduation.
previous link is broken
macOS Big Sur 11 Beta 3 Release Notesfor 62986286.
any other info available?
THX
same for me
EXC_CORPSE_NOTIFY
Application Specific Information:
ProductBuildVersion: 12E262
ASSERTION FAILURE in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-18168/DVTITunesSoftwareServiceFoundation/App Loader/Wrappers/DVTITunesConnectApplicationVersionDescription.m:70
Details: (y) should not be nil.
Object: DVTITunesConnectApplicationVersionDescription: 0x7fb2b6570340
Method: -initWithCoder:
Thread: NSThread: 0x7fb3225777a0{number = 27, name = (null)}
Open FDs: 55/7168
Hints:
Backtrace:
0 -[IDEAssertionHandler handleFailureInMethod:object:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in IDEKit)
1 _DVTAssertionHandler (in DVTFoundation)
I do use 16.0.1 downloaded inside IntelliJ.
it seems working in Xcode 12.5 but we do have a WORSE case.
Suppose You need to write something like that:
struct InfoSheetView: View {
if #available(iOS 15, *) {
} else {
}
var body: some View {
.....
}
}
even if an EMPTY if # I got:
Expected declaration
on if #..
I would like to write
..
if #available(iOS 15, *) {
@Environment(\.dismiss) var dismiss
} else {
@Environment(\.presentationMode) var presentationMode
}
see original example at:
https://www.hackingwithswift.com/quick-start/swiftui/how-to-present-a-new-view-using-sheets
and try to conditionally use
@Environment(\.dismiss) var dismiss
OR
@Environment(.presentationMode) var presentationMode
hello, processors AND chips are different so no way to do it. bootcamp relied on using same Intel chips, so some sort of HW virtualixzation was in place.
bootcamp does rely on Intel x64 binary instructions, and some sort of HW virtualisation, no way to run directly.