Looks like no one’s replied in a while. To start the conversation again, simply
ask a new question.
I need help with Quicktime. I just installed El Capitan and suddenly I cant view any movies shot with my canon digital camera. Kept showing «the document can not be opened, An unknown error occurred (-101). I dont know what to do next since I need those files to view for editing. Thanks
Mac Pro,
OS X El Capitan (10.11.6)
Posted on Sep 9, 2016 8:16 PM
3 replies
Sep 10, 2016 10:09 AM in response to Gerrycondez
I need help with Quicktime. I just installed El Capitan and suddenly I cant view any movies shot with my canon digital camera. Kept showing «the document can not be opened, An unknown error occurred (-101). I dont know what to do next since I need those files to view for editing.
Error code -101 appears to be associated with the scrap heap manager.
More information or a sample file would be useful here. If you upgraded from a pre-Mavericks version of Mac OS X, then knowing the file container format and codecs used to create the files on your camera might be significant. If you upgraded the Mac OS from a post-Mavericks version and are suddenly having problems with the files, then the issue may be either one one of the recent security updates that doesn’t like files created by your Canon digital camera (even though there is nothing wrong with the data) or you may have a bad/corrupted installation of the new operating system. I would normally try playing the files on a different system and/or playing the files in an app like VLC to determine if the problem is with the files themselves or the new operating system, QT structures embedded in the OS or the player app.
Sep 10, 2016 12:14 PM in response to Jon Walker
Thanks, I finally got the quicktime working but it was a very long trial and error process. Installed 10.6, then upgraded to El Capitan, but no good. Installed 10.7.5 then upgraded to El Capitan, no good again. Reinstalled 10.9 Mavericks and upgraded to El Capitan, no good. Installed 10.10 Yosemite and upgraded to El Capitan, no good then finally got a 10.10.1 El Capitan usb, and upgraded to 10.10.6. Now its working. All Quicktime mov playing properly. Also during all the process, the quicktime works properly except installing straight to El Capitan from App Store. If I install Quicktime 7.6, movies also played well without errors except the Quicktime in El Capitan which consistently shows error (-101)
Sep 10, 2016 1:39 PM in response to Gerrycondez
I finally got the quicktime working but it was a very long trial and error process. Installed 10.6, then upgraded to El Capitan, but no good. Installed 10.7.5 then upgraded to El Capitan, no good again. Reinstalled 10.9 Mavericks and upgraded to El Capitan, no good. Installed 10.10 Yosemite and upgraded to El Capitan, no good then finally got a 10.10.1 El Capitan usb, and upgraded to 10.10.6. Now its working. All Quicktime mov playing properly. Also during all the process, the quicktime works properly except installing straight to El Capitan from App Store. If I install Quicktime 7.6, movies also played well without errors except the Quicktime in El Capitan which consistently shows error (-101)
It does sound a bit strange. After reading your response, I decided to run a quick check of a drive on which I recently installed El Capitan. Last weekend I wanted to run some tests on my Mac Mini Server. It is still running under Lion and Server v1.5.0 app and I wanted to check out the latest Server v5.1.7 app. Unfortunately, this meant the tests had to be run under a more current OS, like El Capitan, but I wasn’t willing to update the Mac Mini without preliminary testing. To get around this problem of circular logic, I popped a used 3TB drive into a docking station, erased it, initialized it with El Capitan, purchased/installed the newest Server app and ran my tests. However, it never dawned on me to test an app like the QT 7 Player app at the time.
In any case, I just logged in on that system/start-up drive and tested a number of MPEG-4 AVC files previously stored in the server’s «Sites» folder. They all played without issue on the Mac Mini under last week’s El Capitan install. Since your files now play fine, am wondering if Apple may have had a server download problem or if the ISP for your area has a significant «correctable error rate» problem in their equipment/lines. You may wish to keep an eye out for similar problems in the future just to be on the safe side. Seems like you had to go through a lot of work to get things up and running properly once again. Glad to hear all is well at this time…
Quicktime Error (-101)
How to fix the Runtime Code 101 Quicktime Error 101
This article features error number Code 101, commonly known as Quicktime Error 101 described as Error 101: Quicktime has encountered a problem and needs to close. We are sorry for the inconvenience.
About Runtime Code 101
Runtime Code 101 happens when Quicktime fails or crashes whilst it’s running, hence its name. It doesn’t necessarily mean that the code was corrupt in some way, but just that it did not work during its run-time. This kind of error will appear as an annoying notification on your screen unless handled and corrected. Here are symptoms, causes and ways to troubleshoot the problem.
Definitions (Beta)
Here we list some definitions for the words contained in your error, in an attempt to help you understand your problem. This is a work in progress, so sometimes we might define the word incorrectly, so feel free to skip this section!
- Quicktime — QuickTime is an extensible proprietary multimedia framework developed by Apple Inc A framework called qtkit can be used to develop multimedia applications on top of quicktime.
Symptoms of Code 101 — Quicktime Error 101
Runtime errors happen without warning. The error message can come up the screen anytime Quicktime is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.
There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.
(For illustrative purposes only)
Causes of Quicktime Error 101 — Code 101
During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.
Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.
Repair Methods
Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.
If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.
Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.
Method 1 — Close Conflicting Programs
When you get a runtime error, keep in mind that it is happening due to programs that are conflicting with each other. The first thing you can do to resolve the problem is to stop these conflicting programs.
- Open Task Manager by clicking Ctrl-Alt-Del at the same time. This will let you see the list of programs currently running.
- Go to the Processes tab and stop the programs one by one by highlighting each program and clicking the End Process buttom.
- You will need to observe if the error message will reoccur each time you stop a process.
- Once you get to identify which program is causing the error, you may go ahead with the next troubleshooting step, reinstalling the application.
Method 2 — Update / Reinstall Conflicting Programs
Using Control Panel
- For Windows 7, click the Start Button, then click Control panel, then Uninstall a program
- For Windows 8, click the Start Button, then scroll down and click More Settings, then click Control panel > Uninstall a program.
- For Windows 10, just type Control Panel on the search box and click the result, then click Uninstall a program
- Once inside Programs and Features, click the problem program and click Update or Uninstall.
- If you chose to update, then you will just need to follow the prompt to complete the process, however if you chose to Uninstall, you will follow the prompt to uninstall and then re-download or use the application’s installation disk to reinstall the program.
Using Other Methods
- For Windows 7, you may find the list of all installed programs when you click Start and scroll your mouse over the list that appear on the tab. You may see on that list utility for uninstalling the program. You may go ahead and uninstall using utilities available in this tab.
- For Windows 10, you may click Start, then Settings, then choose Apps.
- Scroll down to see the list of Apps and features installed in your computer.
- Click the Program which is causing the runtime error, then you may choose to uninstall or click Advanced options to reset the application.
Method 3 — Update your Virus protection program or download and install the latest Windows Update
Virus infection causing runtime error on your computer must immediately be prevented, quarantined or deleted. Make sure you update your virus program and run a thorough scan of the computer or, run Windows update so you can get the latest virus definition and fix.
Method 4 — Re-install Runtime Libraries
You might be getting the error because of an update, like the MS Visual C++ package which might not be installed properly or completely. What you can do then is to uninstall the current package and install a fresh copy.
- Uninstall the package by going to Programs and Features, find and highlight the Microsoft Visual C++ Redistributable Package.
- Click Uninstall on top of the list, and when it is done, reboot your computer.
- Download the latest redistributable package from Microsoft then install it.
Method 5 — Run Disk Cleanup
You might also be experiencing runtime error because of a very low free space on your computer.
- You should consider backing up your files and freeing up space on your hard drive
- You can also clear your cache and reboot your computer
- You can also run Disk Cleanup, open your explorer window and right click your main directory (this is usually C: )
- Click Properties and then click Disk Cleanup
Method 6 — Reinstall Your Graphics Driver
If the error is related to a bad graphics driver, then you may do the following:
- Open your Device Manager, locate the graphics driver
- Right click the video card driver then click uninstall, then restart your computer
Method 7 — IE related Runtime Error
If the error you are getting is related to the Internet Explorer, you may do the following:
- Reset your browser.
- For Windows 7, you may click Start, go to Control Panel, then click Internet Options on the left side. Then you can click Advanced tab then click the Reset button.
- For Windows 8 and 10, you may click search and type Internet Options, then go to Advanced tab and click Reset.
- Disable script debugging and error notifications.
- On the same Internet Options window, you may go to Advanced tab and look for Disable script debugging
- Put a check mark on the radio button
- At the same time, uncheck the «Display a Notification about every Script Error» item and then click Apply and OK, then reboot your computer.
If these quick fixes do not work, you can always backup files and run repair reinstall on your computer. However, you can do that later when the solutions listed here did not do the job.
Other languages:
Wie beheben Fehler 101 (Quicktime-Fehler 101) — Fehler 101: Quicktime hat ein Problem festgestellt und muss geschlossen werden. Wir entschuldigen uns für die Unannehmlichkeiten.
Come fissare Errore 101 (Quicktime Errore 101) — Errore 101: Quicktime ha riscontrato un problema e deve essere chiuso. Ci scusiamo per l’inconveniente.
Hoe maak je Fout 101 (Quicktime-fout 101) — Fout 101: Quicktime heeft een probleem ondervonden en moet worden afgesloten. Excuses voor het ongemak.
Comment réparer Erreur 101 (Erreur Quicktime 101) — Erreur 101 : Quicktime a rencontré un problème et doit fermer. Nous sommes désolés du dérangement.
어떻게 고치는 지 오류 101 (퀵타임 오류 101) — 오류 101: Quicktime에 문제가 발생해 닫아야 합니다. 불편을 드려 죄송합니다.
Como corrigir o Erro 101 (Quicktime Error 101) — Erro 101: O Quicktime encontrou um problema e precisa fechar. Lamentamos o inconveniente.
Hur man åtgärdar Fel 101 (Quicktime Error 101) — Fel 101: Quicktime har stött på ett problem och måste avslutas. Vi är ledsna för besväret.
Как исправить Ошибка 101 (Ошибка Quicktime 101) — Ошибка 101: Возникла ошибка в приложении Quicktime. Приложение будет закрыто. Приносим свои извинения за неудобства.
Jak naprawić Błąd 101 (Błąd Quicktime 101) — Błąd 101: Quicktime napotkał problem i musi zostać zamknięty. Przepraszamy za niedogodności.
Cómo arreglar Error 101 (Error 101 de Quicktime) — Error 101: Quicktime ha detectado un problema y debe cerrarse. Lamentamos las molestias.
About The Author: Phil Hart has been a Microsoft Community Contributor since 2010. With a current point score over 100,000, they’ve contributed more than 3000 answers in the Microsoft Support forums and have created almost 200 new help articles in the Technet Wiki.
Follow Us:
This repair tool can fix common computer problems such as blue screens, crashes and freezes, missing DLL files, as well as repair malware/virus damage and more by replacing damaged and missing system files.
STEP 1:
Click Here to Download and install the Windows repair tool.
STEP 2:
Click on Start Scan and let it analyze your device.
STEP 3:
Click on Repair All to fix all of the issues it detected.
DOWNLOAD NOW
Compatibility
Requirements
1 Ghz CPU, 512 MB RAM, 40 GB HDD
This download offers unlimited scans of your Windows PC for free. Full system repairs start at $19.95.
Article ID: ACX010091EN
Applies To: Windows 10, Windows 8.1, Windows 7, Windows Vista, Windows XP, Windows 2000
Speed Up Tip #82
Uninstall Programs Completely:
Use tools like Revo Uninstaller clean up every bit of scraps left behind when you do a normal uninstall. Third-party uninstallers help prevent unnecessary files from building up as well as keep useless registry files and libraries away from getting stuck in your system.
Click Here for another way to speed up your Windows PC
Номер ошибки: | Ошибка 101 | |
Название ошибки: | Quicktime Error 101 | |
Описание ошибки: | Ошибка 101: Возникла ошибка в приложении Quicktime. Приложение будет закрыто. Приносим извинения за неудобства. | |
Разработчик: | Apple Inc. | |
Программное обеспечение: | Quicktime | |
Относится к: | Windows XP, Vista, 7, 8, 10, 11 |
«Quicktime Error 101» Введение
Люди часто предпочитают ссылаться на «Quicktime Error 101» как на «ошибку времени выполнения», также известную как программная ошибка. Программисты, такие как Apple Inc., стремятся создавать программное обеспечение, свободное от этих сбоев, пока оно не будет публично выпущено. К сожалению, некоторые критические проблемы, такие как ошибка 101, часто могут быть упущены из виду.
Пользователи Quicktime могут столкнуться с сообщением об ошибке после выполнения программы, например «Quicktime Error 101». После того, как об ошибке будет сообщено, Apple Inc. отреагирует и быстро исследует ошибки 101 проблемы. Затем Apple Inc. исправит ошибки и подготовит файл обновления для загрузки. Чтобы исправить такие ошибки 101 ошибки, устанавливаемое обновление программного обеспечения будет выпущено от поставщика программного обеспечения.
В чем причина ошибки 101?
В большинстве случаев вы увидите «Quicktime Error 101» во время загрузки Quicktime. Мы можем определить происхождение ошибок ошибки 101 во время выполнения следующим образом:
Ошибка 101 Crash — Ошибка 101 остановит компьютер от выполнения обычной программной операции. Это возникает, когда Quicktime не работает должным образом или не знает, какой вывод будет подходящим.
Утечка памяти «Quicktime Error 101» — если есть утечка памяти в Quicktime, это может привести к тому, что ОС будет выглядеть вялой. Это может быть вызвано неправильной конфигурацией программного обеспечения Apple Inc. или когда одна команда запускает цикл, который не может быть завершен.
Error 101 Logic Error — Ошибка программной логики возникает, когда, несмотря на точный ввод от пользователя, производится неверный вывод. Обычные причины этой проблемы связаны с ошибками в обработке данных.
Как правило, такие Apple Inc. ошибки возникают из-за повреждённых или отсутствующих файлов Quicktime Error 101, а иногда — в результате заражения вредоносным ПО в настоящем или прошлом, что оказало влияние на Quicktime. Обычно, установка новой версии файла Apple Inc. позволяет устранить проблему, из-за которой возникает ошибка. Мы также рекомендуем выполнить сканирование реестра, чтобы очистить все недействительные ссылки на Quicktime Error 101, которые могут являться причиной ошибки.
Распространенные сообщения об ошибках в Quicktime Error 101
Quicktime Error 101 Проблемы, связанные с Quicktime:
- «Ошибка в приложении: Quicktime Error 101»
- «Ошибка программного обеспечения Win32: Quicktime Error 101»
- «Извините, Quicktime Error 101 столкнулся с проблемой. «
- «Файл Quicktime Error 101 не найден.»
- «Отсутствует файл Quicktime Error 101.»
- «Ошибка запуска программы: Quicktime Error 101.»
- «Не удается запустить Quicktime Error 101. «
- «Quicktime Error 101 остановлен. «
- «Ошибка пути программного обеспечения: Quicktime Error 101. «
Проблемы Quicktime Error 101 с участием Quicktimes возникают во время установки, при запуске или завершении работы программного обеспечения, связанного с Quicktime Error 101, или во время процесса установки Windows. Выделение при возникновении ошибок Quicktime Error 101 имеет первостепенное значение для поиска причины проблем Quicktime и сообщения о них вApple Inc. за помощью.
Истоки проблем Quicktime Error 101
Заражение вредоносными программами, недопустимые записи реестра Quicktime или отсутствующие или поврежденные файлы Quicktime Error 101 могут создать эти ошибки Quicktime Error 101.
В частности, проблемы с Quicktime Error 101, вызванные:
- Поврежденная или недопустимая запись реестра Quicktime Error 101.
- Вирус или вредоносное ПО, повреждающее Quicktime Error 101.
- Другая программа (не связанная с Quicktime) удалила Quicktime Error 101 злонамеренно или по ошибке.
- Другое программное обеспечение, конфликтующее с Quicktime, Quicktime Error 101 или общими ссылками.
- Поврежденная установка или загрузка Quicktime (Quicktime Error 101).
Продукт Solvusoft
Загрузка
WinThruster 2022 — Проверьте свой компьютер на наличие ошибок.
Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11
Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление
-
#1
Hi. I did a clean install of Lion on a new system. It boots fine, graphics seem to be working with no problems, the only thing is that quicktime X gives me a (-101) error when I try to play h264 or mp4 files (apple.com/trailers for example), however it does play ProRes files. Quicktime 7 will play the files that X won’t, but lags for a few seconds before beginning playback.
I have installed the DSDT for my system, and am using Chimera v1.4.1 r877. I tried updating to 1.5.4 but I would lose video once it reached the login screen after boot, so I reverted to v1.4.1
I have noticed that it will flash «unsupported card» during boot…
System specs:
GA-H55M-UD2H-F9
i3-540
Diamond Radeon HD 6450
2gb patriot
32gb SSD boot drive
Any help would be great
-
#2
I tried formatting and reinstalling Lion on this drive — same problem occurs. However I have done installations with this same Lion installer that didn’t have this problem….
I even put this drive into another hackintosh I built with completely different hardware and the same problem occurs. Here are the specs of the other machine:
i7 980X
GA-X58A-UD3R (rev. 2.0) FF
XFX Radeon HD 5770
3X4GB Corsair
So as far as I can tell, the only things that could possibly be causing the problem are the drive itself or the DSDT (which I got from the DSDT database), or maybe somehow the lion installer damaged itself since the last time I used it… So frustrating…
Any help would be much appreciated
Edit: I just tried changing the DSDT to a version for a newer BIOS, same problems.
-
#3
not that it solves your problem…but what happens when you use VLC?Thanks
R.
-
#4
VLC seems to work on the files QTX won’t play, looks like it also doesn’t lag as much as QT7
-
#6
Same problem here. Fresh Lion install, 10.7.2. VLC works fine for all files. Verified files play with QTX on other machines (MacBook white 2007). Just installed Chimera 1.7.0.
Intel i5-2500k
Gigabyte Z68MX-UD2H-B3 F11
Integrated graphics (Intel HD 3000)
Corsair XMS3 DDR3 8GB
-
#7
Happened to me today. Fresh Lion install as well.
-
#8
What happens if you use GraphicsEnabler=Yes?
These issues are usually graphics related. Is your DVD player working? Chess?
-
#9
In my case, it was audio related. Turns out I didn’t have my speakers plugged in to audio port (green), so no audio device was detected. Once plugged in and system rebooted QuickTime worked fine.
-
#10
big up bungduh!!!
had the same problem. reattached my speakers, rebooted and bingo. thanks man.
Actual Behavior
Running my debug configuration for iOS doesn’t work. I get the error:
Error while executing command 'react-native run-ios --scheme 'dev' --simulator='iPhone SE' --verbose --no-packager' (error code 101)
Expected Behavior
Debugging should work as normal
Software versions
- React-Native VS Code extension version: 0.11.1
- VSCode version: 1.38.1
- OS platform and version: Darwin x64 18.7.0 (macOS Mojave Version 10.14.6)
- NodeJS version: 10.11.0
- React Native version: 0.57.8
- Expo SDK version (include if relevant): Not using Expo
Launch configuration
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Debug iOS",
"cwd": "${workspaceFolder}",
"type": "reactnative",
"request": "launch",
"platform": "ios",
"runArguments": ["--scheme 'dev'", "--simulator='iPhone SE'", "--verbose"]
},
]
}
Outputs (Include if relevant)
- Output of the Debug Console (View -> Toggle Debug Console):
OS: darwin x64
Adapter node: v10.11.0 x64
vscode-chrome-debug-core: 6.7.46
Could not debug. Error while executing command 'react-native run-ios --scheme 'dev' --simulator='iPhone SE' --verbose --no-packager': Error while executing command 'react-native run-ios --scheme 'dev' --simulator='iPhone SE' --verbose --no-packager' (error code 101)
- Output of the React-Native output channel (View -> Toggle Output -> Select React-Native in ListBox):
[Info] Packager is already running.
[Info] Prewarming bundle cache. This may take a while ...
[Info] About to get: http://localhost:8081/index.bundle?platform=ios
BUNDLE [ios, dev] ./index.js ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ 100.0% (1/1), done.
::ffff:127.0.0.1 - - [24/Sep/2019:19:52:33 +0000] "GET /index.bundle?platform=ios HTTP/1.1" 200 8435064 "-" "-"
[Warning] The Bundle Cache was prewarmed.
[Info] Building and running application.
[Error] Error: Error while executing command 'react-native run-ios --scheme 'dev' --simulator='iPhone SE' --verbose --no-packager': Error while executing command 'react-native run-ios --scheme 'dev' --simulator='iPhone SE' --verbose --no-packager' (error code 101)
- Output of the Developer Tools console (Help -> Toggle Developer Tools -> Select Console tab):
In my app I show more apps with SKStoreProductViewController, but the Apple store review team rejects it with the reason:
«An error message displays when tapping on the more apps button.»
Everything works fine when I test it on my devices.
Below is the screenshot Apple sent me, what could be the problem?
Sample code:
__weak typeof(self) weakSelf = self;
SKStoreProductViewController* vc = [[SKStoreProductViewController alloc] init];
vc.delegate = self;
[vc loadProductWithParameters:@{SKStoreProductParameterITunesItemIdentifier : @1000000000} completionBlock:^(BOOL result, NSError * _Nullable error) {
if(result==NO){
//handle failure
return;
}
[weakSelf presentViewController:vc animated:YES completion:nil];
}];
asked Nov 3, 2014 at 17:21
3
ITMLKitErrorDomain
errors frequently occur when a SKStoreProductViewController
tries to call loadProductWithParameters
with invalid parameters. Example full error:
<Warning>: [SKStoreProductViewController]: Did fail with error: Error Domain=ITMLKitErrorDomain Code=101 "The operation couldn’t be completed. (ITMLKitErrorDomain error 101.)" UserInfo={ ... } {ITMLKitErrorHTTPStatus=400}
Verify you do not have any typos or unexpected keys in your parameters
dictionary when calling loadProductWithParameters
. Verify the values for keys such as SKStoreProductParameterITunesItemIdentifier
and SKStoreProductParameterAffiliateToken
are valid.
answered Mar 3, 2016 at 14:50
JALJAL
41.3k23 gold badges167 silver badges296 bronze badges
If you are not experiencing this issue on test devices, just send it to review again, this could be a temporary issue with itunes site (it is used to show these «more apps», isn’t it?). There are several mentions of that problem over the internet without any solution.
answered Mar 3, 2016 at 14:32
GriefGrief
1,7791 gold badge20 silver badges40 bronze badges
0
During investigation of youre issue it is possible to conclude that is quite rare case that could be connected with wrong product id in case of SkProductViewController
. Also you should check if you are trying to show single app or amount of them. Because Apple have bug that is connected with showing of multiple items.
I am using SKStoreProductViewController in this way. This is code block that show app in App Store:
SKStoreProductViewController *storeProductViewController = [[SKStoreProductViewController alloc] init];
[storeProductViewController setDelegate:self];
[storeProductViewController loadProductWithParameters:@{SKStoreProductParameterITunesItemIdentifier : @"xxxxx"} completionBlock:^(BOOL result, NSError *error) {
if (error) {
NSLog(@"Error %@ with User Info %@.", error, [error userInfo]);
} else {
[self presentViewController:storeProductViewController animated:YES completion:nil];
}
}];
Then i use delegate SKStoreProductViewControllerDelegate
like this:
- (void)productViewControllerDidFinish:(SKStoreProductViewController *)viewController {
[self dismissViewControllerAnimated:YES completion:nil];
}
Also i use [button setExclusiveTouch:YES];
because customers some times press few buttons with products. Also test you’re id if it is single product.
answered Mar 3, 2016 at 14:55
Oleg GordiichukOleg Gordiichuk
15k7 gold badges59 silver badges97 bronze badges
I just finished dealing with this same issue. Everything works just fine when testing the app but the App Review team was rejecting my app for showing an alert view with the error returned by the call to loadProductWithParameters
.
I worked around the issue by launching the App Store in Safari if the call to loadProductWithParameters
fails. This provides a useful fallback in the rare cases when SKStoreProductViewController
isn’t working.
SKStoreProductViewController *vc = [[SKStoreProductViewController alloc] init];
vc.delegate = self;
NSDictionary *parameters = @{ SKStoreProductParameterITunesItemIdentifier : someAppId };
[vc loadProductWithParameters:parameters completionBlock:^(BOOL result, NSError *error) {
if (result) {
[someController presentViewController:vc animated:YES completion:nil];
} else {
NSURL *appURL = [NSURL URLWithString:[NSString stringWithFormat:@"https://itunes.apple.com/app/id%@?mt=8", someAppId]];
if ([[UIApplication sharedApplication] canOpenURL:appURL]) {
[[UIApplication sharedApplication] openURL:appURL];
} else {
// display the error in an alert
}
}
}];
answered Oct 6, 2017 at 0:30
rmaddyrmaddy
312k42 gold badges525 silver badges567 bronze badges
I’ve had a rejection for the same reason (2 rejections) and I’ve found that I get this exact error testing without Wi-Fi (on a Wi-Fi only device).
So my thought is that Apple is testing this on a Wi-Fi device (they said they are testing on a Wi-Fi iPad) and they have disabled Wi-Fi. It would be nice if in the rejection they told you about the fact that they were testing with no internet access but you need to read between the lines.
So since you can’t display the controller without an internet connection you need to show an appropriate error like «Please check your internet connection and try again.»
Definitely don’t show the localized description for the Error returned to the user.
answered Mar 8, 2019 at 20:04
EarlyRiserEarlyRiser
7273 silver badges6 bronze badges
Rust language
When you edit the Rust “Thebook” second chapter “guess” game Code in VS Code, try adding a rand dependency in cargo. Toml, which is
cargo.toml
[dependencies]
rand = "0.7.3"
after typing $cargo build on the command line,
is found
Cargo invocation has failed: Error: exit code: 101.
such a popup reminder, prompt crate enable failure.
OUTPUT window prompts as follows:
Running `cargo build --bin=instances --package=instances
--message-format=json`...
Blocking waiting for file lock on package cache
Updating crates.io index warning: spurious network error (2 tries remaining): failed to send request: 操作超时 ; class=Os (2)
warning: spurious network error (1 tries remaining): failed to send request: 操作超时 ; class=Os (2)
error: failed to get `rand` as a dependency of package `instances v1.46.0 (D:DataFilesCodesLearningRUSTInstances)`
Caused by: failed to load source for dependency `rand`
Caused by: Unable to update registry `https://github.com/rust-lang/crates.io-index`
Caused by: failed to fetch `https://github.com/rust-lang/crates.io-index`
Caused by: failed to send request: 操作超时 ; class=Os (2)
it turned out that the connection to Github was timed out. This problem will also be pop-ups for installed updates that are ignored when checking the rust-Analyzer plug-in version every time VS Code is started.
below provides the method to connect to Github. This method also applies to the problem of not being able to connect to Github when a web page is logged on. IP addresses are usually added to the HOSTS file.
host files in C:// Windows/system32/dreivrs/etc directory. You can right click -> Property changes the write permission of User before editing and saving.
can be learned that the current lot by https://github.com.ipaddress.com/www.github.com website IP address has been changed, so a lot of articles referred to in the hosts change have failed. The code added to the hosts file is provided as follows:
#Github
140.82.113.4 github.com
of course, it is more recommended to use the above link to query before making changes, to prevent IP address update invalid. Finally, don’t forget to save the file hosts, , and unwrite User .