As I said, the first hack, can be added to your build.settings without having to hack the Manifest file. The second one is native code which will require enterprise.
Rob
As I said, the first hack, can be added to your build.settings without having to hack the Manifest file. The second one is native code which will require enterprise.
Rob
OK, thanks man.
I asked the developers of the local app market and they told me their differences with Google’s API:
First, the change that should be done in the manifest:
\<uses-permission android:name="com.farsitel.bazaar.permission.PAY\_THROUGH\_BAZAAR"\>\</uses-permission\>
Second, this:
@Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity\_main); bindService(new Intent("ir.cafebazaar.pardakht.InAppBillingService.BIND"), mServiceConn, Context.BIND\_AUTO\_CREATE);
Since I can’t afford the Enterprise edition, my question is if I can build for Google API and then do these changes afterwards. Apparently I can alter the manifest, and my question is the second change that is code which needs to be compiled and added to my APK. Is it possible to do these to the already-compiled-for-Google-API APK?
Thanks!
The first thing you can add to your build.settings. We don’t support manually editing the Manifest file.
The second thing would require Enterprise. Did you approach them about doing the plugin?
Rob
I talked to them about it and even gave David’s email to them but apparently they are not willing to help.
Is there anything else I can do beside Enterprise? Like those hacks I mentioned?
Thanks.
As I said, the first hack, can be added to your build.settings without having to hack the Manifest file. The second one is native code which will require enterprise.
Rob
OK, thanks man.