java - Android Emulator in Android Studio does not show my app -


i'm working on android application using android studio. when run code on nexus 5 api 21 x86 emulator, emulator not show application trying debug. went applications, still cannot find app trying test. however, emulator still show app previous project working on. log doesn't show errors either when compiling gradle , starting emulator.

from researching other posts, believe may have version of emulator running. not sure if case , if how fix it. have pasted copy of manifest below , gradle.build. please let me know wrong, problem has been irritating me last several days.

 <manifest xmlns:android="http://schemas.android.com/apk/res/android"     package="com.jamescho.androidgame"     android:versioncode="1"     android:versionname="0.5" >      <uses-permission android:name="android.permission.wake_lock" />     <uses-permission android:name="android.permission.write_external_storage" />     <uses-sdk         android:minsdkversion="8"         android:targetsdkversion="17" />      <application         android:icon="@drawable/bxbx_char"         android:label="bxbx">         <activity             android:name="com.bxbx.bxbxgame.game"             android:configchanges="keyboard|keyboardhidden|orientation"             android:label="bxbx"             android:screenorientation="portrait">              <intent-filter>                  <action android:name="android.intent.action.main"/>                  <category android:name="android.intent.category.launcher"/>              </intent-filter>         </activity>     </application>  </manifest>

and build.gradle 

apply plugin: 'com.android.application'  android {     compilesdkversion 17     buildtoolsversion "19.1.0"      defaultconfig {         applicationid "com.jamescho.androidgame"         minsdkversion 8         targetsdkversion 17     }      buildtypes {         release {             minifyenabled false             proguardfiles getdefaultproguardfile('proguard-android.txt'), 'proguard-rules.txt'         }     } }  dependencies {     compile 'com.android.support:support-v4:18.+'

from android studio, go avd manager (tools>android>avd). locate virtual device, , under actions, select downward triangle , hit wipe data. should remove old test apk.

if old app still there, try deleting old virtual device , creating new one. if still there, selecting wrong virtual device when starting app.

you should try clearing default testing device. under run>edit configurations, select default run configuration. on general tab, go bottom under deployment target options , select open select target deployment dialog, save , try again.


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more