Iphone app was created using an online platform which no longer exists. Probably a year ago. I am trying to upload to https://www.diawi.com/ now, so that the app can still be used in some fashion.
I originally received an error stating "Error with Payload Directory" and moved the .app folder into a folder called "Payload" and now it seems not be able to find the Info.plist file. Any assistance? I am a bit out of date in my app experience.
App.ipa is located at http://beveragedist.com/app/Payload.ipa
for anyone who can help me troubleshoot the internal file structure.
Related
for my xamarin forms ios project I am getting an error when uploading an ipa file via the application uploader to apple.
missing required icon file ipad of exactly 167x167 for ipad pro.
The weird thing is I have actually included this file already in the media.xcassets.
any idea how to fix this?
So here is what I have found regarding this:
First, I would check that all the information found in this article is done (it talks about making sure your .csproj file has the needed references to the files):
https://alexdunn.org/2020/01/06/xamarin-tip-fixing-missing-ios-app-icons/
Second, I would check for miss-match of the case of letters in the file name between the json file in the Assets.xcassets/AppIcons.appiconset folder and your ios csproj file. For example ipad176.png is not the same as iPad176.png. This article explains it well.
https://blog.mzikmund.com/2020/05/the-mystery-of-the-missing-ios-app-icon/
Finally, neither of these resolved my problem. For me it seemed that one of the entries in my json file had something weird about it (event though visually it looked fine). I noticed that every icon entry in the json file AFTER the one that had something weird about it, showed as missing when I attempt to publish the archive. For me the easiest way to find the offending entry was to look for the first (i.e. earliest in the json list) icon entry that generated a missing icon error message when I published. Then, I unloaded my iOS project, opened the .csproj file for the iOS project in Visual Studio, and found the entry for that first app icon. I then copied the file name from the .csproj file and replace the file name in the json with the copied name, saved the json file and magically, I could publish my archive to the App Store.
When uploading my zip file using the Developer Dashboard, I'm getting the following error:
An error occurred: Failed to process your item.
Can not process the manifest file.,Can not process the message.json file.,Can not process the key.pem file.,Chrome Web Store system error, please try again later.
I've followed 3 different tutorials (2 on extensions, and 1 on uploading to the Developer Dashboard) that I found on creating an extension on Googles' site. None of them say to create a message.json so I didn't create one (not sure why its telling me it can't process it). There is also no key.pem file, as they said do not generate this file and don't include it - as it will be generated when you upload it.
It says try again later, but I've tried several weeks now with no luck.
Currently, I'm exploring if my zip file is generated "funny" from 7-zip. I'd use the built in windows zip once I get that working again - however it seems corrupted.
My manifest file is in the root folder, and and the extension works in developer mode on my chrome. I've quadruple checked that the JSON is valid as well.
The extension works great for me, but fails the upload process.
How do I get past this step of the process?
Make sure manifest.json is in the root of the zip archive (not inside any directory)
Use the standard deflate zipping method in 7-zip, not anything fancy like deflate64
The answer to this was:
In the 7-Zip settings, I was using the compression method Deflate64, I changed it to Deflate and it the zip file was accepted. Thanks to #wOxxOm
I probably wouldn't have had this problem but my windows built in zip is currently corrupted and used 7zip to make a zip file.
So, I'm trying to invoke a Google Could Messaging service from Amazon echo, using NodeJS (using mac os x).
Since my main.js file contains 3rd party libraries, I installed them with
"npm install" command. I'm using the following libraries for sure:
https://github.com/ToothlessGear/node-gcm for NodeJS Google Could Messaging
async
When I made my ZIP file and uploaded to amazon lambda, I got the following error message:
It looks like your Lambda function "oAa" is unable to be edited inline, so you need to re-upload any changes. This may be because your file is too large or your zip file contains more than one file to edit. However, you can still invoke your function right now.
The ZIP file isn't large, it's only 1.5 Mb. I assume I have this error, because the file contains all the libraries I need, with more than one js file.
I've attached the folder structure of my ZIP file. It contains from one file and one folder. I have one file in the main folder, and a tons of libraries next to it (inside the second folder).
UPDATE
this is the error message what I get:
{
"errorMessage": "Exception: TypeError: Cannot read property 'application' of undefined"
}
and this didn't work as a solution:
https://forums.developer.amazon.com/forums/message.jspa?messageID=18330
Did any of you met with the same issue in the past? May I kindly ask for your help, guys ?
Thanks,
Karoly
I got it to work by not zipping the directory (and contents) but by adding the contents of the directory to a zip archive. Basically, I removed the upper level directory. AWS Lambda's UI was able to locate my .js then.
It's hard to tell what exactly the problem is with Alexa, did you make sure you filled out the configuration and event sources tab correctly (this would be under the AWS part). Did you update your application ID? This is the biggest pain in the butt. Did you just upload your zip folder and click test? (which is incorrect).
I don't think this is an error, per se. I get this frequently and my skills still work without problem. I believe all this means is that "your Lambda function xxxx is unable to be edited inline". You will have to continue editing in an external editor and uploading the zip instead of being able to edit in Amazons lambda text editor.
I think the TypeError in your update is an unrelated issue.
I was receiving this error and solved it by looking at CloudWatch logs. You will see much more detailed error messages in there, and a log will be created each time you try to run your function.
I am hoping someone has had this issue before and can help me resolve. I was working on a company project. I had just finished up and needed to publish my project to the server. When trying to publish, I got the error "This file is currently not available for use on this computer."
So then I tried to open one of the .cs files of the solution, and the error occurred again from trying to open the file. So I tried to grab the latest version from TFS thinking it would give me whichever file is missing, but when I click "Get Latest Version" on the project, the error message pops up there too.
I thought surely I will be able to delete the project locally and then remap it, but I can't even delete the project off my computer, as the error message pops up halfway through deletion. When it occurs there, however, I do get "Error 0x800710FE: This file is currently not available for use on this computer."
Also have tried deleting offline cached files through Control Panel > Sync Center > Manage Offline Files > Disk Usage > Delete temp files
I got this error for a small, test solution that was not using TFS. The default file location is the documents folder, which in my environment is synced using the Sync Center. I moved all of the solution files to a new local folder that was not included in Sync operations and the error went away.
Conclusion: storing VS files in a folder managed by Sync Center is likely a bad idea.
I got this error when trying to save an excel file served from a webpage.
The solution for me was to save it under a different filename. Possibly because I previously had a file with the same name open in excel.
I'm having problems uploading and even viewing files in the File section of MODX Revolution 2.2.3-pl. When I try to upload a file, all I get is "Upload error". Nothing shows up in the Filesystem area, just a folder called Media that doesn't let me do anything. Any ideas of what might be going on?
As far as file system permissions go, all folders are set to 755 and all files are set to 644. I'm seeing this behavior logged in as admin/sudo. I just moved my installation of MODX from my local machine, where I believe it worked right, to a shared hosting environment, and that's where I'm seeing this issue.
There has been a recent update to 2.2.4-pl after reported problems with the file manager.
I'd recommend updating to 2.2.4-pl and check if the problem is still present.
Also it could be that your MOD system settings have Use Multibyte Extension enabled but PHP hasn’t been compiled with the –enable-mbstring option.
Hidden away in the MODx Media Browser is a failed response to a JSON request and an error message showing…
Fatal error: Call to undefined function mb_strtolower() in on line 168
If you can’t recompile PHP or just need to get your Media Browser working again, go to System Settings and set Multibyte Extension to No.
All the credit to [Max Mitchell's Post].1