Per the comments on the question, it appears that the solution is that the developer needs to use the Partner WSDL, or generate a new Enterprise WSDL that includes the missing objects for their Sandbox organization.
The issue is most likely that you've used the (generic) com.salesforce.androisdk account type on more than one app—e.g. one of the sample apps and your new app—on your emulator/device. The Mobile SDK doesn't find the account initially for your new app, but then ends up trying to access the account from the previous app, and so you run into bind failures, ...
The DreamforcengerHunt code that you are refering to was written 2 years ago - before the force.com Mobile SDK existed - as a result, it does not provide out of the box oAuth, REST API wrappers for firing SOQLs and several other features that the SDK provides.
Just so you know, the app you referred to was re-written as a hybrid Mobile SDK app one year later ...
This link provides exactly what you need - a basic step by step tutorial to create a barebones Salesforce Android native app using Mobile SDK - http://www2.developerforce.com/mobile/getting-started/android
When you are ready to get beyond Hello World, I strongly recommend looking at the REST Explorer sample app that comes bundled with the SDK - https://...
So you want the hexadecimal (base 16) representation for the MD5 hash for your input string?
Have a look at Generate MD5 hash in Java and From string to hex MD5 hash and back. There is an answer there from Jon Skeet that uses Hex.encodeHexString from the Apache Commons Codec to do the Hex encoding of the MD5 hash.
// For MessageDigest
I've seen this earlier. This can happen on emulator when your hybrid app is invoking Visualforce pages and the root cause is same as when you'd see this issue in a web application. This thread explains the issue and the solution.
In most cases, the culprit would be the requestData parameter. If you do not need it, remove it. Also, you can use add a remote ...
This line: Caused by: java.lang.NoClassDefFoundError: com.exacttarget.etpushsdk.ETLocationManager$RegionMonitor
indicates that the reason for the crash is that it is unable to find RegionMonitor which is a class defined within ETLocationManager.
Do you have Proguard turned on? If so, please review the Proguard statements in proguard.cfg which we use for ...
If you have more than 1 service declared in your application then there's a Google bug in their GcmReceiver which may be getting in your way. See https://salesforce.stackexchange.com/a/128740/16482 for details, but net-net-net, manually declare the ETPushReceiver in your manifest and ensure that it is the 1st service listed.
It's ridiculous because HTML5 date input works in regular Android browsers so they did something extraordinary to break it. I'm surprised you say "recently", I've encountered it in June-July and for me it was always broken (testing on HTC ONe X):
I've ended up conditionally including the jQueryMobile's datepicker and displaying either native date picker or ...
Your success method is actually named onSuccessSfdcChatter while the method you are registering as a callback with forcetk is called onSuccessSfdcAccounts- make sure you use the correct success method handler name that's registered with forcetk
Salesforce provides an excellent array of options for this starting from their excellent Platform Mobile Services site, where depending on your architecture preferences for your mobile client application you can choose an appropriate of SDK type. As you've pointed out, either way the Salesforce REST API is key aspect. These SDK's provide access to this API ...
You can check in your android application if a device is connected to internet or not :-
// Call android connectivity services. Require "android.permission.ACCESS_NETWORK_STATE"
ConnectivityManager connectManager = (ConnectivityManager) getSystemService(Context.CONNECTIVITY_SERVICE);
NetworkInfo currentNetworkInfo = connectManager....
The RestRequest object (which you initially construct one of with the getRequestForQuery method), has a generic constructor which you can use for the queryMore case.
RestRequest queryMore = new RestRequest(RestMethod.GET, nextRecordsUrl, null);
You can then use the RestRequest object the exact same way as before by passing it to sendAsync on your ...
SFDC Support(Case #10889926) told me:
Our R&D confirmed that this is already a known issue and is subjected
to be fixed in Winter 15 release (around October, subject to change).
I have added the case BUG number to the case so that when the fix is
released you would be notified on the same.
Please let me know if there are any further ...
When experiencing errors that are clearly raised from the server side, a good place to start is the system status page at trust.salesforce.com. At the time you seem to be accessing it, there appear to be some problems for the instance you are hitting. If you are new, your instance is in your URL:
The SDK requires an Application Class as the context in readyAimFire().
We completed additional testing of this scenario, and have found that you cannot call readyAimFire() within an Activity class, even if you pass in activity.getApplicationClass(). You must call readyAimFire() from the Application class.
This is because the application class will be ...
I ran into this issue recently and it looks like having a string reference for the category name value causes a problem.
To resolve the issue you need to replace few values in this file.
Replace all occurrences of
<category android:name="@string/app_package" />
Check the docs for Push Configuration Troubleshooting:
One of the most common problems is customers creating their app in the App Center with the Android Key rather than the Server Key, but using a REST client like PAW and trying to send directly ...
I came across this, too when doing a simple example. The "No account of type xyz" isn't really an error, just an informational message from the account manager. The real issue is the "bind error".
For the Authenticator Service to work properly, you need to define it in your AndroidManifest. The easiest way to do this is to just add "manifestmerger.enabled=...
Above is the knowledge developer API guide and please refer chapter 4 (Second half).All the REST API's provided by salesforce related to knowledge module is discussed in depth.
Also using salesforce SDK will mean lot of time saving as
already the code for the ...
OK, thanks to @ThomasTaylor, I found out that the answer turned out to be Connected Apps settings under Setup/Administration Setup/Manage Apps/Connected Apps. I'd never been to this page to my knowledge and I'm the only one who uses this SFDC account, so I'm not sure if this was a default setting or if was changed somehow.
The Permitted Users for ...
Your code looks good as long as your constants for ET_APP_ID, ET_APP_TOKEN, and GOOGLE_PROJECT_ID are all correct. Step 1 is to make sure there are no copy/paste mistakes there.
If that all checks out, you should next check your AndroidManifest.xml file and ensure it has all of the required permissions, Receivers, and Services. Also ensure your ...
This is similar to the question asked here.
The Mobile SDK uses REST API while the client ID / Token is defined only for the SOAP API and goes in the CallOption.client. Unfortunately, there isn't a direct equivalent for the REST API that will populate the Client Id. Instead you can get you app whitelisted by Salesforce.
If you have a partner app you should ...
You are totally right.
Sadly, the field it is working at all in Android. ( But it is working in iOS, browser... )
Just tested your version with a custom object and also with opportunity object ( in Android and in iOS) , however none of them are working in Android app.
I also got a nice error like :
Unfortunately, Salesforce1 has stopped.!
Maybe the best ...
I had 2 copies of android.jar included in the project. It seems it got included while importing project. I removed the duplicate from Android Private Libraries where only third party jars are kept. This resolved the issues.
Thanks @Bill for your help.
You cannot create a new Custom Object using REST API. New custom objects can only be created using Metadata API.
The API you are referring is used to create a new record of said object (be it Custom or Standard). See this for more information about the api, specifically For an example of creating a new record using POST, see Create a Record.
You're not expected to use this flow, so it is unlikely that the Android mobile toolkit would include code to do this. It is a security risk, and it also is a red flag that will prevent your app from passing a security review and being listed on the AppExchange.
If you really want to do this, you're going to have to write all the logic for it yourself, by ...
Take a look at this learning app. In particular, pay attention to the dependencies in the app/build.gradle file and the <application> tag in the AndroidManifest.xml file.
Without any data other than is provided in your question it sounds like you've missed the Gradle dependencies and you must create a Class that extends Android Application. You tell ...