问题:

我正在通过从GitHub测试一些项目来使用Android Studio,当我尝试模拟apk时,它不允许我选择模拟器。

它告诉我:

设备支持x86,但APK仅支持armeabi-v7a

为什么这样做呢?

I am playing around with Android Studio by testing some projects out from GitHub and when I try to emulate the apk, it does not let me choose an emulator.It tells me:Device supports x86, but APK only supports armeabi-v7aWhy does it do this?

问题:

注意:我正在开发使用Xamarin。 类似的问题发布在Xamarin论坛这里

我正在创建一个名为CompanyApp的应用程序。 然后我为com.Company.CompanyApp创建了一个App ID,以及使用相应App ID的Distribution Provisioning Profile。 我上传了二进制文件,它工作得很好。

然后我继续创建应用程序的演示版本(基本上是相同的应用程序,只需要很少的修改,因此它是相同的解决方案和项目,只是不同的捆绑签名设置), CompanyAppDemo带有新的App ID com.Company.CompanyAppDemo ,以及新的分发配置文件,它使用新的App ID。 我更新了iOS Bundle Signing选项以使用新的Provisioning Profile并生成了IPA。 但是当我将其上传到Application Loader时,我收到以下错误:

[2015-01-23 16:08:21 SGT]错误:错误ITMS-90164:“无效的代码签名权利。您的应用程序包签名中的权利与供应配置文件中包含的权利不匹配。根据配置配置文件,捆绑包含一个不允许的密钥值:’TEAMID.com.Company.CompanyApp’,用于’Payload / CompanyApp.app / CompanyApp’中的密钥’application-identifier’

[2015-01-23 16:08:21 SGT]错误:错误ITMS-90046:“无效的代码签名权利。您的应用程序包的签名包含iOS不支持的代码签名权利。具体来说,价值’TEAMID.com.Company .CompanyApp’不支持’Payload / CompanyApp.app / CompanyApp’中的密钥’application-identifier’。该值应该是以TEAMID开头的字符串,后跟一个点’。’,后跟包标识符。“

我已经调试了好几天才弄明白无济于事。

我想知道为什么当我使用新配置文件签名时,Application Loader抛出的错误引用了原始TEAMID.com.Company.CompanyApp的ID而不是TEAMID.com.Company.CompanyAppDemo ? 这是Xamarin中的一个错误,它找错了配置文件或者我错过了什么? 对于不同的应用程序,您不需要不同的证书吗?

请注意,在更改Xamarin中的iOS Build Signing选项之前,我始终在XCode> Preference中刷新了Provisioning Profile列表。

Note: I’m developing using Xamarin.Similar question posted in Xamarin Forum hereI’m creating an app called, say CompanyApp .Then I created an App ID for it com.Company.CompanyApp , along with Distribution Provisioning Profile that uses the corresponding App ID.I uploaded the binary and it worked perfectly fine.Then I went on create a demo version of the app (basically the same app with small modification, so it’s the same solution & project, just different bundle signing setting), CompanyAppDemo with a new App ID com.Company.CompanyAppDemo , along with a new Distribution Provisioning Profile that uses the new App ID.I updated the iOS Bundle Signing options to use the new Provisioning Profile and generated the IPA.But when I uploaded this to Application Loader, I got the following error:[2015-01-23 16:08:21 SGT] ERROR: ERROR ITMS-90164: “Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: ‘TEAMID.com.Company.CompanyApp’ for the key ‘application-identifier’ in ‘Payload/CompanyApp.app/CompanyApp'”[2015-01-23 16:08:21 SGT] ERROR: ERROR ITMS-90046: “Invalid Code Signing Entitlements. Your application bundle’s signature contains code signing entitlements that are not supported on iOS. Specifically, value ‘TEAMID.com.Company.CompanyApp’ for key ‘application-identifier’ in ‘Payload/CompanyApp.app/CompanyApp’ is not supported. This value should be a string starting with your TEAMID, followed by a dot ‘.’, followed by the bundle identifier.”I have been debugging for days to figure out to no avail.I am wondering why when I signed with the new profile, the error that Application Loader threw refer to the ID of the original TEAMID.com.Company.CompanyApp instead of TEAMID.com.Company.CompanyAppDemo ?Is this a bug in Xamarin that pick up a wrong provisioning profile or am I missing something?You don’t need different certificate for different app right?Note that I have always refreshed the Provisioning Profile list in XCode > Preference before changing the iOS Build Signing option in Xamarin.

问题:

尝试连接到mysql的数据库时我面临的问题。 我还提供了我使用过的数据库设置。

 Traceback (most recent call last):
 File "manage.py", line 10, in <module>
 execute_from_command_line(sys.argv)
 File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 453, in execute_from_command_line
utility.execute()
File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 272, in fetch_command
klass = load_command_class(app_name, subcommand)
File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 77, in load_command_class
module = import_module('%s.management.commands.%s' % (app_name, name))
File "/home/arundhati/Desktop/test/testprac/local/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module
__import__(name)
File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/core/management/commands/syncdb.py", line 8, in <module>
from django.core.management.sql import custom_sql_for_model, emit_post_sync_signal
File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/core/management/sql.py", line 9, in <module>
from django.db import models
File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/db/__init__.py", line 40, in <module>
backend = load_backend(connection.settings_dict['ENGINE'])
File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/db/__init__.py", line 34, in __getattr__
return getattr(connections[DEFAULT_DB_ALIAS], item)
File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/db/utils.py", line 93, in __getitem__
backend = load_backend(db['ENGINE'])
File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/db/utils.py", line 27, in load_backend
return import_module('.base', backend_name)
File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module
__import__(name)
File "/home/ar/Desktop/test/testprac/local/lib/python2.7/site-packages/django/db/backends/mysql/base.py", line 17, in <module>
raise ImproperlyConfigured("Error loading MySQLdb module: %s" % e)
django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb module: No module named MySQLdb

数据库设置::

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql', # Add 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
        'NAME': 'ar_test_db',                      # Or path to database file if using 
        # The following settings are not used with sqlite3:
        'USER': '',
        'PASSWORD': '',
        'HOST': '',                      # Empty for localhost through domain sockets or   '127.0.0.1' for localhost through TCP.
        'PORT': '',                      # Set to empty string for default.
    }
}

非常感谢您的帮助 !!

The problem Im facing while trying to connect to database for mysql.I have also given the database settings that i have used.Databse Settings::Thanks a lot for the help !!

问题:

我正在尝试在Xcode中生成UItest。 当我尝试刷UIview时出现错误:

Timestamped Event Matching Error: Failed to find matching element

错误窗口

在此输入图像描述

如果我尝试点击UIView,也会发生这种情况。

I’m trying to generate a UItest in Xcode.When I try to swipe UIview I get an error:error windowThis also happens if I try to tap UIView.

问题:

我运行几个替换命令作为mavencolorize脚本的核心。 其中一个sed命令使用一个正则表达式,它可以在shell中找到,如下所述 可以在此处找到当前(不工作)的实现。

当我将该命令的一个变体包含到脚本中时,会出现不同的行为:

变式1:

$ sed -re "s/([a-zA-Z0-9./\\ :-]+)/\1/g"

适应脚本:

-re "s/WARNING: ([a-zA-Z0-9./\\ :-]+)/${warn}WARNING: \1${c_end}/g" \

错误: shell输出的信息与我输入$ sed信息相同。 奇怪!?


变式2:

$ sed -e "s/\([a-zA-Z0-9./\\ :-]\+\)/\1/g"

适应脚本:

-e "s/WARNING: \([a-zA-Z0-9./\\ :-]\+\)/${warn}WARNING: \1${c_end}/g" \

错误:

sed:-e表达式#7,char 59:`s’命令的RHS上的引用\\ 1无效

I run several substitution commands as the core of a colorize script for maven .One of the sed commands uses a regular expression which works find in the shell as discussed here .The current (not working) implementation can be found here .When I include one of the variants of the command into the script different behavior occurs:Variant 1:Adapted to the script:Error: The shell outputs the same information as if I would type $ sed .Strange!?Variant 2:Adapted to the script:Error:sed: -e expression #7, char 59: invalid reference \\1 on `s’ command’s RHS