-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get translations does not support format parameter anymore #7
Comments
Some response would have been nice, guess we stick to the old API then. |
Hello, this is Charlie from OneSky, sorry for the belated response. Can you kindly share with me your account ID on OneSky? You can send the information to [email protected], and I will further help in migrating the API for this case. Best, |
@cowcow02 could you share this information publicly? I cannot migrate as well since i need the "symfony" xliff format. |
@cowcow02 any news? |
Hello guys. This is Ruby from OneSky. Our customer success managers are available at [email protected] to assist any Classic API transition. @francescolaffi Please contact us via your registered email so that we can help on your case. Thank you for using OneSky! |
Same here, is there something new ? |
Hey, we are just migrating from the old API. Before, there was a "format" parameter when downloading the files, so you could download the same translations for example for Android as xml and iOS as strings file. Now you only seem the get to format that was uploaded. What do you expect us to do now? Converting the files by script is an option, but not very fail-safe.
https://api.oneskyapp.com/2/string/download
vs.
https://platform.api.onesky.io/1/projects/???/translations
Best regards,
jkoepcke.
The text was updated successfully, but these errors were encountered: