@scott wait so you were able to release on Samsung store again?
@spacewolf yes I was. I did get an email from Samsung a while ago that stated: “This is to inform you that you have been pre-defined as a ‘Partner’ of Samsung Apps based on your past app registration and partnership. You can register apps without any limitations where we look forward to your next app registration.”
So, that could likely be the reason it worked fine.
So… I have been doing apps for Samsung for a while now and really would not like to lose the ability to develop for their store. There is a clause in the rule that indicates that if you are a partner, then you do not need to use their sdk. More specifically they wrote to me:
“This is to inform you that you have been pre-defined as a ‘Partner’ of Samsung Apps based on your past app registration and partnership. You can register apps without any limitations where we look forward to your next app registration.”
I’m sure others received similar emails or could ask to be partners.
Along with that, I was just informed by Nook that my current builds are not comparable with their new device. What can be done about this?
Scott
Scott - I know that a Corona app built with a recent build will run fine on the new Nook device(s). If they told you about such an issue, it’s probably because the app was made with a fairly old build of Corona. So you probably just have to re-build with a more recent version of Corona.
To add on to what David said, with regards to “new” Nook devices: starting with Daily build 2264, we switched our Android to a minimum 2.3.3 version to support the required changes by Google’s advertising solutions. According to B&N’s Nook site:
Nook Color: Android 2.2
Nook Tablet: Android 2.3 (note, not 2.3.3)
Nook HD and HD+: Android 4.0.4
B&N is now pushing some variant of the Samsung Galaxy Tab instead of their Nook specific brands, so they should have a more modern Android on them.
From this, the Nook Color will require building with a build before 2264. The Nook Tablet may or may not work because I don’t know if the major version is sufficient or not. Even though the site says 2.3, they could run 2.3.something and only show 2.3, so for that device, your mileage may vary.
Rob
Thank you David and Rob.
Question on Nook, which build would be sufficient for it to work? Do I need to go to a minimum build of 2264 or more?
And then as far as Samsung goes… will choosing “none” as the target app store be sufficient for Samsung? Or was their something special that was added when we used to select Samsung?
Scott
One more question… I am guessing since the new Nook Samsung Tablet is having problem running older Corona built Apps that there are likely a lot of newer devices (like a standard Samsung Galaxy Tab 4) that they are going to be crashing on?
Scott
You should be able to build for modern Nook devices with any build of Corona SDK. You must use a build older than 2264 to build for the Nook Color. For the Nook Tablet, I’m unsure because the specs say It’s Android 2.3 and I don’t know if 2.3.3 will run on it or not, but clearly 2263 or earlier will work on the Nook Color.
As for Samsung, the only support we had was for the native.showPopup() for ratings and going to the app store’s page for the app. It has zero to do with Samsung’s new requirements.
If you want to submit to Samsung, you won’t be able to use native.showPopup() to get to their store access for ratings or showing links to other apps.
Any news on supporting Samsung store?
Best thing about samsung store - they do full QA for apps. SO far best and hardest QA i even seen on mobiles. And that is just to get approved there. That is a great thing - no need to hire external testers =)
We are not supporting the Samsung store at this time and probably won’t be in the near future until they drop the requirement to build using their SDKs. If this is important to you, you can use Corona Enterprise and access their SDK’s from native land, or convince an Enterprise customer to build the Samsung SDK’s as a plugin and sell it through the Gremlin Interactive plugin store.
Rob
Ok, I just wanted to follow up.
I was able to successfully get a new app on the Samsung Market by setting market to None when building.
Scott
@spacewolf yes I was. I did get an email from Samsung a while ago that stated: “This is to inform you that you have been pre-defined as a ‘Partner’ of Samsung Apps based on your past app registration and partnership. You can register apps without any limitations where we look forward to your next app registration.”
So, that could likely be the reason it worked fine.