Provision profile is empty

I’ve done quite a bit of work with Oxygene for Cocoa against the simulator.
Now I’m trying against a device
I set up a certificate, and VS sees that
However it does not see the provisioning profile I set up for my app, where the AppID in the provisioning profile matches the Application ID in VS.
Can anyone suggest how I encourage VS via crossbox to see my provisioning profile - like where I put it so crossbox sees it - or what I may have missed when setting the provisioning profile up, making it not display

Thanks!

I’m assuming at this point that when Oxygene for Cocoa looks for an Application ID, this is in fact a bundle ID.

If that assumption is flawed, maybe that’s where the problem lies…

Oh hang on. I was using KeyChain Access and the Apple web site.

I’d totally forgotten about the Xcode Organizer window (found it again by locating http://wiki.oxygenelanguage.com/en/Setting_up_Xcode ). That seems to be helping me forward. I’ll be back if I continue to have problems.

Things improved with Xcode’s involvement
I got a team provisioning profile and that shows up in VS via crossbox.
However it shows up in a simple project as:

iOS Team Provisioning Profile: Wildcard AppID (unknown profile)

When I build the app it immediately fails saying Provisioning profile “iOS Team Provisioning Profile: Wildcard AppID” not found on “MyCrossBoxServerName”. Make sure you have the correct ID

Help!!!

Incidentally, I tested how Xcode fares without doing anything else - just creating new project and having it run on the phone -> no issues, nothing to setup nothing to tweak. Just ran it on the phone.

Oxygene is having issues though

I haz a sad :o(

Lol. Even Delphi can successfully launch to the device with no effort in setting config values. How vexing that Oxygene is struggling.

If only I knew what/where it was looking for the thing it can’t find.

In here:

http://wiki.oxygenelanguage.com/en/Setting_up_Xcode

it says “As part of it’s connection to your Mac via CrossBox, Oxygene for Cocoa in Visual Studio on tour<sic> Windows PC or VM will automatically pick up both your provisioning profiles and code signing certificates.”

Ok, so I need to know how to control/diagnose this location of profiles by crossbox, please…

did you maybe re-download or update the profile? the .oxygene project stores the profile by ID, not name. seeing a name and “unknown profile” usually means that the profile cant be found by ID. re-selecting it from the drop-down should adjust that. I’ll think about how we can improve this (maybe by falling-back to the same-named profile and issuing a warning during compile, if no profile is found by id)

Oh, so it’s been burned into the oxygene file.

Ok, I see it. Useful to know.

I chose the blank profile, then re-chose the single listed profile after a refresh of certs & profiles.

No change

Then I deleted it and the certificate ref from the oxygene file, reloaded in VS, and my certs still show, but it now shows no profiles in the list, despite both other cited tools happily working with my device.

Please suggest what to do next to get Oxygene to see my profile

“did you maybe re-download or update the profile?” -> maybe, I was trying all sorts to get it to work. It occurred to me at one point to try the other tools, and “It Just Worked”…

Ok, so 1313 has 63004 and resolves it.

excellent.