A few feature requests.

[zeyangl]

Great helper library. Much better than the complicated yet incomplete cocos official sdkbox. Code clarify is great, and I find it really easy to add extra features not found in current version. Overall really great work.

Feature requests:

1. It would be nice to have Facebook/Twitter share success returned, or allow passing in a completion callback. iOS supports this natively.
2. It would be nice to support InApp billing and receipt verification. Cocos-helper as complete as it is, still sends me to use another iap sdk.
3. It would be nice to not having to set strings in values.xml. I'm not sure what the motivation is, but having Facebook app id scattered in 2 places seems inconvenient.

[SonarSystems]

Great feature requests.

Regarding Social callbacks, this is very interesting and we will take a look into this.

Regarding IAP it is being worked on, we understand that this is probably the most needed feature for Cocos Helper.

Regarding App ID scattering, we will also take a look.

[zeyangl]

Another feature request is to finish the currently half-baked Facebook login. Some facebook permissions(like publish_posts) require a functional login button, even all you do is login and nothing else.

Another feature request is to fix all the warnings. I now compile in Xcode 7 against iOS 9 sdk. Get a bunch of warnings. It's nothing serious though.

Just some additional thoughts.
If you guys care to do a majority solution for Chinese developers, then get QQ and Sina Weibo. Both are as popular as WeChat. All 3 cover like 95% game developer needs in terms of social sharing. Even sdkbox does not do this, which surprises me. ShareSDK is a functional alternative but its implementation is a bit too heavy weight, and bloats the package size.

[SonarSystems]

Thanks for the suggestions, feel free to post all future suggestions on our feature request page http://www.sonarsystems.co.uk/cocoshelper.php?type=featurerequest

[zeyangl]

Also it would be nice to have Chartboost response delegate call a C++ lambda callback or something like that. Probably a ChartBoost::RegisterResponseHandler(std::function<> handler). Not getting any callback event is a pretty serious drawback. Is it better to post on the featurereuqest URL? The github format seems better for discussion, and a lot more accessible.

[SonarSystems]

Feature requests yes but for more discussion based on here.

So you would put on Sonar Learning that you want QQ and Sina Weibo and post it more in depth on github if you wanted to talk about it.