Rectangle 27 25

I recently ran into this issue with XCode 8 just after updating my device from iOS 9 to 10. The exact error I received was:Development cannot be enabled while your device is locked. Please unlock your device and reattach. I received this error even when my phone was unlocked, and after unplugging and re-plugging in the device.

As is mentioned in several answers, the device is locked message is actually referring to the device not trusting the MacBook. In my case, I think my phone defaulted to not trusting my computer after updating to iOS 10. Here are the steps that worked for me to reset the settings (this is the same process that is mentioned in the Apple support page in tehprofessors' answer):

Settings > General > Reset
Reset Location & Privacy
  • Plug your device back into your computer, and on the device you will be prompted to trust the computer. Tap trust.
  • Rebuild in XCode and the device locked error should disappear.

yep unfortunately only this worked for me on from Xcode 8 on iOS 10 :(

@BishalGhimire Yeah, it's definitely not ideal. I actually just had to do this reset again as XCode started giving me the device is locked message again without any noticeable changes to any of my iPhone's settings or XCode's settings. Somewhere along the way my trust settings for my computer are being reset, but I'm not sure when and where.

you should wait for a while to processing symbol files

Hmm... this fixed the "Device Locked" error ... but has replaced it with a "Could not save the pairing record." error ...

ios - Xcode "Device Locked" When iPhone is unlocked - Stack Overflow

ios iphone xcode
Rectangle 27 74

I had this issue after updating to a newer patch version of ruby. Unfortunately the header files gem "debugger-ruby_core_source" was locked in to an earlier version in the Gemfile.lock so it didn't have the required header files.

All you need to do is update that gem by doing:

bundle update debugger-ruby_core_source

You should be able to bundle install afterwards.

If you aren't using bundler then just install the latest version before trying to install debugger:

debugger-ruby_core_source
gem install debugger-ruby_core_source-1.3.5.gem Successfully installed debugger-ruby_core_source-1.3.5 1 gem installed  C:\RubyGems\lib\debugGems>gem install ruby-debug-base19x-0.11.29.gem Temporarily enhancing PATH to include DevKit... Building native extensions.  This could take a while... ERROR:  Error installing ruby-debug-base19x-0.11.29.gem:         ERROR: Failed to build gem native extension.          C:/Ruby193/bin/ruby.exe extconf.rb checking for vm_core.h... no

@Arpit this fix is for the gem 'debugger' github - not sure it works with windows but you could give it a try....

Yeah.. already installed the debugger gem. Now, the question is - How to tell this to RubyMine? (it's still searching for ruby-debug-base19x)

ruby on rails - An error occurred while installing debugger-linecache ...

ruby-on-rails ruby gem gemfile
Rectangle 27 74

I had this issue after updating to a newer patch version of ruby. Unfortunately the header files gem "debugger-ruby_core_source" was locked in to an earlier version in the Gemfile.lock so it didn't have the required header files.

All you need to do is update that gem by doing:

bundle update debugger-ruby_core_source

You should be able to bundle install afterwards.

If you aren't using bundler then just install the latest version before trying to install debugger:

debugger-ruby_core_source
gem install debugger-ruby_core_source-1.3.5.gem Successfully installed debugger-ruby_core_source-1.3.5 1 gem installed  C:\RubyGems\lib\debugGems>gem install ruby-debug-base19x-0.11.29.gem Temporarily enhancing PATH to include DevKit... Building native extensions.  This could take a while... ERROR:  Error installing ruby-debug-base19x-0.11.29.gem:         ERROR: Failed to build gem native extension.          C:/Ruby193/bin/ruby.exe extconf.rb checking for vm_core.h... no

@Arpit this fix is for the gem 'debugger' github - not sure it works with windows but you could give it a try....

Yeah.. already installed the debugger gem. Now, the question is - How to tell this to RubyMine? (it's still searching for ruby-debug-base19x)

ruby on rails - An error occurred while installing debugger-linecache ...

ruby-on-rails ruby gem gemfile
Rectangle 27 3

I ran into this issue as well. For some I would like to point out that if it is locked CHECK WITH YOUR TEAM. Someone on the team might have some things locked because they are working on it (this allows developers to do work on things without others coming in and trying to work on the same content as well). If that is the case, releasing the lock and then updating has the potential to lose data for the developer who locked it.

With that in mind my concern was that the "clean up" option would possibly change my working copy or remove information from the Repo level of Subversion. That is not the case. The answer worked for me. Mine became locked when I clicked cancel during the middle of an update. I ended up pulling some of our branches and I did not need the stuff so I hit cancel. My working copy became locked. I could not find any documents that came up as "locked" when I used the command 'release lock'. This left me puzzled and upon some quick reading (and this thread) I attempted the 'clean up' command. After a clean up it resolved my issue and nothing was locked anymore.

tortoisesvn - Working copy locked error in tortoise svn while committi...

svn tortoisesvn
Rectangle 27 1

There's an approximate performance limit of 1 write transaction per second to an entity group. The whole group does get locked for the update. A subsequent transaction will fail and retry.

10k entities in an entity group sounds like a lot, but it really depends on your write patterns. For example, if only a few entities in the group are ever updated, it may not be a big issue. However, if random users are constantly updating random entities in the group, you'll want to split it up into more entity groups.

"performance limit of 1 write transaction per second" - does this mean that it will take ~5 seconds to complete 5 simultaneously issued transactions (on entities of the same group)?

That can happen, since there's some auto-retry in the transaction infrastructure. It's also possible that the first few transactions will succeed and the later ones might just fail (this is more likely with more traffic)

There are two types of entities per group. Entities of first type (a few thousands) change rarely (few times a week), the second type entities (a few thousands also) will change several times a day.

Does it matter if there is no actual conflict between the updates? I expect the occasions when two transactions attempt to update the same entity to be very rare.

When you put them in the same entity group, you limit the whole entity group. Essentially, if you put entities in the same entity group, they're treated as one in terms of transactions. If you want better performance, you want your entities to be in separate groups. Because of that you usually want to keep the number of entities in a group to a minimum if possible.

google app engine - performance implications of transactions on large ...

python google-app-engine transactions google-cloud-datastore app-engine-ndb
Rectangle 27 0

I was updating a website via FTP. I assume the website was in use and when trying to update the bin folder, a couple of the DLL files must have been locked and did not update.

There I saw the error 500 page and on setting of the customErrors mode to be Off, saw the error message mentioned by the OP.

The problem was I did not see the failures listed in the FTP program. I retried those failed fails and they uploaded. The last DLL file updated. So the site then worked.

c# - Error message 'Unable to load one or more of the requested types....

c# entity-framework