After several attempts I have succeed to packaged one extension by using instructions from this PDF - http://info.magento.com/rs/magentocommerce/images/packagingmagentoconnectextensions6%200.pdf
Everything looks good, but when I try to upload the extension, it throws an error, saying that the filename should be in the format XXXXXX-1.0.0 format without the extension, where xxxxxxxxx is my form key, but when I try to upload the renamed copy of the packaged file (one that Magento connect manager extension generated), it throws these 2 errors:
An error occurred during upload to channel MagentoConnect 1.0: Unable
to upload new release XXXXXXXXXXXXXXX-1.0.0.tgz
An error occurred
during upload to channel MagentoConnect 2.0: Package
AnattaDesign_AbandonedCarts not found
I did a bit of research on the error and got to know this has been an issue with Magento in the past and people were facing the exact same issue. On some of them, I found #rondata replying back who was the community manager in back those days, but not sure if he still is.
So any clue how can I get this issue resolved? Whether it could also be an issue with how I packaged the extension? Or may be who is the current community manager and where can I seek some escalation on their uploader bug?
So I think I know what the reason is. When you are asked for the extension key when creating a new extension on magentocommerce.com, don't add the form key over there as your extension key. It's meant to be something unique like Namespace_Module.
When you do that, the error should go away and you should be all good!
Related
I recently submitted an update to my Android app, and I got an error regarding a storage permission that I was using.
I fixed the error that was mentioned, and uploaded a new AAB. While uploading the AAB I got an error about a defective version for a library that is included in my AAB.
Is there any way I can check all the errors from the console at the same time? I would like to avoid fixing the current error, and finding out that another one will be reported on the Google Play console, it would be helpful to receive all errors at the same time.
No, there is no way to do this, because this is done on Google Play's servers and keep changing because of changes on policies and supported versions.
BUT, it is fairly easy to drag & drop aab file to an internal testing track to find if there is a problem or not, and sometimes it will show you more than one error.
I have an App that uses Admod and Firebase from Google. Since I am using Swift they want me to use frameworks when loading them from CocoaPods. When I try to archive/validate the App I get the error:
No suitable application records were found. Verify your bundle identifier 'org.cocoapods.GoogleToolboxForMac'
What is the correct way to provision an app that uses someone else's frameworks so it can be uploaded to iTunes Connect? I tried to find something in Apple's documentation but I haven't found anything.
UPDate:
I previously had answered my own question, since I had thought I had found a solution. My reply was:
Problem Solved. Turns out I was using an App-ID that I am having Apple look into as being corrupt. I had already created a new App-ID to prove the one I want to use is not working and retried with that and it Validates. This required a lot of help from the Google Ads Mobile SDK team. Thanks.
So the correct answer is: Now Incorrect
You should not get this error unless you are using a Bundle-ID that is not already registered on iTunes Connect, but, you should never be able to create an archive that does not have a Bundle-ID that is not already registered on iTunes Connect. So this is caused by an abnormal situation.
This is no longer true
I used my new working project and got 4 whole builds out of it and into iTunes Connect. In the process I was trying to clean up the mess caused by trying to solve this problem, like loosing my git history. I tried to modify my old App to get it to work and without modifying my new working project, But my new project started failing with the above error. I even used my time machine and went back to the directory as it was when I made the last build, but no help. So, any answers?
Further Update:
I pulled all the code related to Google Firebase and Admob out of the code and removed the cocoaPods and Archived/Validated and now I get the error:
You must supply a CFBundleIdentifer for this request.
Which is the error message I was getting with my other App-ID that tracked that App-ID in iTunesConnect. This time it does not track the App-ID so it must be something in my project. Will report what I find.
UpDate:
I think Apple has been modifying their code for validation at the same time I was trying different things. At one point it told me I was using CFBundleSignature instead of CFBundlePackageType set to APP and I fixed this and got the code to validate. Understand I am copying complete projects and renaming everything to debug this problem, so this must have come from the original program. I ended up with a project that was renamed from my original but archived/validated but when I went to compile for Test I got errors that I debugged until I got lots of Mach-O link errors. I decided to complete the loop and go back to my original code and try using the new Bundle-ID which points to the new App-ID, the one that works, and add all the knowledge I have learned. But when I get it done I have an project that can test but does not validate. The only difference is this project has the old identifier which has the same name as the suffix of the App-ID that has a bug.
Am I missing something?
Final UpDate?
On a whim I renamed the Scheme file to be the same as my Suffix to the Bundle-ID and I got my original Project to Validate! I have worked on this for over a month and you might not believe the astonishment I feel in this.
Back to Unit Test!
I have come to the conclusion that the Identity of the App, the name at the far top of the right side Utilities window, has something to do with the way iTunes Connect validates the App. This is the name in the left hand column of the Organizer window. It is like it overrides the suffix of the Bundle-ID and since I can't use that Identifier because the associated App-ID is corrupt. Or the name of the Scheme.
I'm getting an error in the admin page when I try to login, it was working fine and I would like to know if you can please help find out what may be causing the error and how to fix it. The error is:
Fatal error: Class 'Magpleasure_Filesystem_Helper_Data' not found in /home/site/public_html/app/Mage.php on line 546
The admin page is only showing the header and the error line code, the search box but the search box is not giving any results neither. However, the front of the store is working find, no issues in front. Please help, thank you
Best Regards,
Jenny
99% that you were hacked and that you didn't apply the two patches which were released by magento some weeks ago...
I have seen that issue 1 day ago at a client side of mine and they also didn't apply the patch.
check also this: https://magento.stackexchange.com/questions/64461/error-logging-in-the-admin-panel-fatal-error-class-magpleasure-filesystem-help
It also happened to me. Did not install the security patches.
Follow the steps from this post:
https://magento.stackexchange.com/questions/64461/error-logging-in-the-admin-panel-fatal-error-class-magpleasure-filesystem-help
Remove all files: app/code/community/Magpleasure/Filesystem/
Clear your cache, login should be possible now.
Check for new "Admin Users"
Patch your System with SUPEE-5344!
This happened to my site AGAIN, even after removing the magepleasure files, and then installing the 2 security patches.
I looked in the community and local folders as noted above in the way that I fixed this the first time around. This time there was one called Ma2.
I deleted the files from both places and deleted the cache folder contents on the server. I was then able to get the backend again. There was another unauthorized user, deleted it.
There is a remaining problem though. Anybody know where to look to fully delete the problem?
This is Compiler Error edit index.php, there just comment out following lines
$compilerConfig = MAGENTO_ROOT . '/includes/config.php'; if
(file_exists($compilerConfig)) {
include $compilerConfig; }
it will fix now..
This looks like an extension has been installed but not completely. The error is because Magento is trying to find the file Magpleasure_Filesystem_Helper_Data which I guess will either be under code base local or community app/code/local/Magpleasure/Filesystem/Helper/Data.php but the file is not there.
I would suggest reinstalling the extension either by magento connect or locally and deploy to your system and if you are still having issues contacting the developer directly may be your best bet.
When I tried to use an Ajax control toolkit, I get a grey out error and searching around they said installing VS10 Service pack could help to solve the problem. So I did install it and now I got a serious problem:
I can no longer load the website that I can load normally before, it shows this error:
Server Error. 500 - Internal server error.
I tried many ways and finally found this one looks quite close to what happened to me:
http://support.microsoft.com/kb/842329
And I tried what it suggested:
go to C:\Windows\system32\mcfc42.dll-> properties\security\Edit\Add
Added:
Iwam_computername or computername\Iwam_computername
Also added:
Everyone
Allow Full control to all.
Restart server. But still the same problem. Please help me to fix this problem, unfortunately my server did not install backup option before I install VS SP1 so I could not recover to the previous point. Any solution ? If I cannot access it, no way I can code and test my website...
I found the solution for this. At first, to narrow down the problem I load the website at server side (not at client side) then I see this error lines in my web.config file, I think when I click at property at project in VS and choose .net 4.0 then back to 3.5 it add some duplicate to my web.config file. I just add all the first lines related to .net 3.5 and keep the xml format correct then it works fine now! Many thanks !!
But all I get from my Connect Manager is the following message:
community/Mage_GoogleShopping: Version for 'Mage_GoogleShopping' was not detected
If I try and use the version 1 extension key all I get is:
Couldn't resolve host 'magento-core'
I am using a mostly fresh install of Magento Community 1.5.0.1 (I say mostly because we do have our own template but it is very basic).
Anyone have any luck installing this extension. GoogleShopping is a huge boon to our hit count and the recent changes to the google products API has really affected our implementation.
this extension is still in alpha stability, you need to change your preference settings ("settings" tab in your magento connect manager) for "preferred state"
OSdave had the right answer ... but the way I fixed the error message was I blew away the download folder on the server and re-copied over from the original Magento install package.
Once I had done that I re-ran the Extension Key in Connect and this time it actually said. "That Extension is in Alpha stage. You'll need to change your preferences to install it."
I did NOT get the error above anymore. At that point everything worked like a charm.