Simulator

[taglia3]

Can Bagel's Mac app debug network request/response from the iOS Simulator?

[yagiz]

Yes. It can detect simulators. It can even detect whole simulators that run Bagel enabled projects in the same network. @taglia3

[taglia3]

Thanks @yagiz .

In my case the Mac's app doesn't seem to find any simulator / device. Maybe have I to configure come option on my Mac?

If I provide custom configuration on the iOS App it crashes to full stack trace.

i.e.

let bagelConfig = BagelConfiguration()
        
bagelConfig.project.projectName = "Custom Project Name"
bagelConfig.device.deviceName = "Custom Device Name"
bagelConfig.device.deviceDescription = "Custom Device Description"
        
Bagel.start(bagelConfig)

[taglia3]

I've solved my issue by changing in the Mac's app code the values of the Bagel.entitlements property from:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.security.app-sandbox</key>
	<true/>
	<key>com.apple.security.files.user-selected.read-only</key>
	<true/>
</dict>
</plist>

to:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.security.app-sandbox</key>
	<false/>
	<key>com.apple.security.files.user-selected.read-only</key>
	<false/>
</dict>
</plist>

[yagiz]

Changing the values of the Bagel.entitlements properties fixes this issue but there shouldn't be a call loop in the first place. I'm on it. @taglia3

[digoreis]

@yagiz can close this issue?