To publish app to China we need to provide The Computer Software Copyright Certificate. How to have The Computer Software Copyright Certificate to provide Huawei AppGallery?
The official site doesn't work and returns 400 Bad Request when trying to access the Copyright Section
Also the English version of the site doesn't work and returning this ->
Also for some unknown reasons when the site looks like working sometimes, i can't register since don't have any Chinese phone number.
Does anyone face the same issue or is there any other way to get that kind of Certificate elsewhere to be able to publish the app to China Mainland?
What is the best guideline to follow to easily be certified and be able to operate with China App Markets ?
Related
I am looking to develop my IOS application to communicate with iXpand Flash Drive using lighting port. I am going to use iXpand SDK for that. The flash drive is defined in public database of apple. Does this need me to have MFI Program to deploy the app on App Store?
I can answer it well as I have deal with the same case:
You need not to have MFI License, as you are not manufacturer of
iXpand Flash Drive Hardware.
The SDK does not communicate with WesternDigital to get any information.
In my case, Apple Does not have asked for MFI details for iXpand. You may just need to provide details harware details for using lighting port.
At last but not least, we cannot 100% sure about apple review process. They can accept / reject with any reason but here you have good chances to accept it if you have valid reason to us external hardware.
I am very new to coding and tech talks but I am working with a client who needs help on how to get their OTT app on major ISPs'set-top boxes. Anything around app SDK for specific ISPs, examples on how Dysney+ or Netflix get their app on boxes, which ISP uses which language, which technology do ISPs uses to charge application on their boxes (qml, HTML, ? ) would help me a lot! Apologies if my question is very generic but I don't understand much on this subject.
Thank you very much in advance for your time and help.
When you mention 'ISP' set-top boxes, I assume you're asking how to get the app on the box people get when they sign up for cable TV. For example, if you want your client's app pre-installed on the Comcast Xfinity set-top box, you should contact Comcast so they can provide instructions to make your request.
If you're referring to how you can get your client's video app on common OTT devices such as Roku, you should search that device's website on how to create a developer account. For example, here are details on how to create a Roku channel (app) that people can download onto their Roku device at home.
https://developer.roku.com/docs/developer-program/publishing/channel-publishing-guide.md
When your channel is tested and ready to deploy, you publish it using the Developer Dashboard. If the channel is a public channel that will be offered on the Roku Channel Store, it will be reviewed by Roku during the certification process. If you are updating an existing channel, you will also publish it using Developer Dashboard.
Prerequisites and guidelines for creating a public channel
To assure success in creating a public channel, you will need to:
Create your design assets following Design and User Experience Guidelines.
Go through the Pre-certification Check List.
Package your Roku channel.
Publish your channel (this page).
Cheers.
With Apple getting ever more stringent by enforcing 2FA on all iOS accounts, a unique challenge that we've encountered is how to setup a system where Apple’s 2FA codes for a shared dev account can be forwarded to perhaps our private slack channel? Hence enabling multiple members on a team access to Apple’s services.
I got so annoyed by this that we then developed a hack.
It’s a Python script that’s running in a terminal on the mac mini CI machine and using some vision SDK tooling, checks the screen every few seconds for the 2FA dialog pop-up.
If it finds it, it then navigates the pop-up, crops the 2FA code, does OCR on it, and relays the code through the Slack API to a dedicated internal buildbot channel that our devs get notified on.
Sample cropped 2FA code screenshot:
The result, is the general shared apple id account is now much more convenient and efficient to access by our devs for CI/CD or any other client App Store info updates.
So that’s one way to do it. 😎
I use Firebase database, storage etc. in my application. When I uploaded my archive to Itunes Connect, it has asked me a questions about crypting. Do I use crypting in my application and etc.
I know, that Firebase uses https.
So the question is: If I use Firebase, what should I answer on this questions?
As of September 20th, 2016 (Dentons) the answer is almost always No. Unless you are a encrypted message provider like Signal, Telegram, Whatsapp or Snapchat - these export controls are no longer a concern. Nearly every app uses HTTPS these days and it defeats the purpose of the U.S. Export Registry if every app needs to be registered.
The countries that are export restricted are people you don't normally want as customers; Syria, North Korea ect... and are typically restricted from using apps for more fundamental reasons - like not having cellphone towers or even the ability to buy a cellphone. It is common for backend services like Firebase and Google to blacklist export-restricted IP spaces, so they won't be able to connect even if they get the app.
I wonder if anyone tried using Kaazing for client push with Silverlight? How did it go?
http://www.kaazing.org/confluence/display/KAAZING/What+is+Kaazing+Open+Gateway
Speaking as a representative of Kaazing:
Eikos Partners won an innovation award for their application, EPOC, which is an equity trading system running with Silverlight and Kaazing. They have screenshots of their application on their site.
Note that you need the commercial version of Kaazing Gateway to get access to Silverlight support. You can download it from here after you click on "Accept License Agreement."
You can also read up on Kaazing Gateway and Websockets here.