A note for others playing with Salesforce SDK with WIRE.

It appears fusebox is latching on to your SDK settings the first time they are inputted. Resulting in errors if a key is inputed incorrectly or a URI is not matched. The best way to remove this issue is to wipe your SF app from fusebox (swipe left on your app name) and delete, then snapshot and download it fresh from within fusebox.

We also recommend that you select "Full Access" from the API Setting pane within your Salesforce account for the app. We will correct the documentation linked above to avoid any confusion.

Steve, looks like your engine version in the studio is 1.4. You need to bump that up to 1.5.2 to get access to SalesForce and make sure to have the latest Fusebox build on your device.

Please feel free to email me directly during the hackathon! ajones@rarewire.com

We'll work on getting a standard SDK walkthrough together for the community today.

The invalid datasource error is due to an incorrect Application Key on the Salesforce side, which we'll resolve with the walkthrough.

Thanks for attending!

Did you happen to give your .p12 file a password? If so, this could be the issue. Our provisioner can only accept .p12 files that have no password protection per our tutorials on the subject.

You may try updating your app name from Vita di Gesù to Vita di Gesu. The special character might be causing the issue.

Ad-Hoc builds do require that you upload at least one icon and splash screen from the Platform Settings section of your app. Please add these and try again.

Steve,

Might need to have a look at the code to get a better look, but before we do that...lets try one more thing.

Create a texttemple like so:

<texttemplate name="sessionTokenOut"><![CDATA[X-Parse-Session-Token="[preferences:sessionToken]"]]></texttemplate>

Then in an action do the following:


<assign property="preferences:sessionToken" value="[datasource:tokenAuth.1.token]" />
<assign property="httpheader:appToken.Authorization" value="[template:sessionTokenOut.content]" />


Steve,

You can use an assign like so, that appends your htttpheader request whenever you need to update it.

<assign property="httpheader:datasourceName.X-Parse-Session-Token" value="[YOUR VALUE]" />

My first thought would be to talk you out of the addition of PARSE credentials on the API Setting page for this usage. Here is why, if you depend on a RW live-app-update to push new Parse keys, if a used declines an update from the app, they won't be pushed to your production level services. I would take any need for the user to respond out of this workflow.

What would be easy to set up and for the team to manage would be to create a little datasource in the app that points to an external json file with a single name:vale pair.


<datasource name="bestof" source="URL" query="/app/status" providertype="json"/>


and the json file be something like:


{
"app": {
"status": [
{
"level": "sandbox"
}
]
}


when the app loads, fire that datasource and return the result. depending on the result, set up a couple if statements that set a [var:statusURL] to the url you want and then in any place in the app that references that URL, replace it was your [var:statusURL].

Hope that helps.

The only time you can determine the keyboard is when using the textfield object. Then you can utilize the kbtype attribute to select a different keyboard type.

At this time the keyboard action cannot specify a keyboard.