Am trying to push an APK to the Google Play Store, and am having issues.
When am trying to upload images it is not accepting.
They mentioned like image format should be 24-bit PNG alpha.
How to convert images to this format?
Related
I can't upload images to the Google Play store in order to put my app in production.
None of the images can be uploaded, I checked 50 times, the size is good and I tried as png, jpg, jpeg, etc without success.
Here are the screenshots of my tries:
What could be wrong?
Edit: I have the same problem to upload the apk and the problem seems to come from CORS policy but deactivate it does not change anything...
The solution until November 2, 2020 is to use the classic Google Play Console in private mode. There, image uploading is working as intended.
I am developing an android app, where I require to upload image/video files really quick. What could be the best approach to do the same? I am using windows azure media server.
I researched and went through the entire documentation on Azure yet couldn't find the right solution for the below problems. So, I am elaborating the list of issues and scenarios for your understanding.
Just to add top-up on this issue. Following are the scenarios.
We are uploading the video through app. - Need help is optimising the upload transfer rate by using viable compression.
As of now it is taking approximately 1-2 mins to complete the upload.
Post uploading the Video we crop the video using FFmpeg codecs in our application on VM and then move the video file to Blob Storage.
Followed by that we use the Azure Media SDK to make an asset to encode the cropped video for adaptive streaming and we also create the Progressive Download file for downloading the video which is cropped and has stiched images with it.
Cropped and Unstichhed video is played in the app which is of max length 32 seconds.
This still shows the buffering on the 4G network which is questionable?
Downloadable file which has images stiched with it comes out with noise in the bottom of the video. (Attached image for ref.) Ref. Image. Look at the right botton pixelation.
Our Xamarin forms app supports both Android and IOS. This app uses a lot of png images on each and every screen.
We are looking for a better approach to deal with it. Whether to download a zip of png images and maintain them locally (or) download each png image on demand and cache it. It's ok if the application takes bit more time at the time of login. Could you please suggest.
There are instructions here as to how to upload files in Firebase. But the issue is how to resize images when we upload it in firebase from a webpage. I could not find any method in the Firebase API . And no need to paste any code here as well I think.
Shouldn't I try to resize it after I upload the image ? How to do that ?
There is no built-in way to resize an image in the Firebase Storage API. You will either need to resize it before uploading, or download the image in a server-script, resize it and then re-upload the resized image.
You can use firebase cloud function for this task.
I've written an module to resize image files uploaded into a specific folder
https://github.com/kriptontr/fireImgOptimizer
I noticed that all my browsers:
Mozilla Firefox
Google Chrome
Microsoft Edge
Internet Explorer
seem to ignore image EXIF orientation data.
But other programs are orienting the images when they are opened/displayed:
Google Mail
MS Paint
IrfanView
Windows Explorer
We have a webpage on which users can upload images. I am asking, because users are complaining that the uploaded images look diferent/rotated than when opened on their local device using an image viewer. It seems to become an icreasing problem as more and more users are using smartphones and cameras to upload images directly without using any image editing software.
Here you can find some example images that have EXIF data in their header: https://github.com/recurser/exif-orientation-examples
Question: Since the browsers are ignoring the EXIF orienting should one auto-apply them on the uploaded images and then strip them from the header? Why are browsers ignoring EXIF information? What to do?