Databases
StackOverflow2013
Postsdbo
POAndroid App crashes due to adding a layout
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid App crashes due to adding a layout
    primarykey
    data
    text
    <p>I have the following initialization in my java file:</p> <pre><code>Button btnCalc = (Button) findViewById(R.id.btnCalculate); final Button btnClearWin = (Button) findViewById(R.id.btnClear); final Button btnSaveTrip = (Button) findViewById(R.id.btnSave); final EditText nameOfInf = (EditText)findViewById(R.id.etName); final EditText tollAmount = (EditText)findViewById(R.id.etToll); final EditText showLog = (EditText)findViewById(R.id.etShowLog); showLog.setFocusable(false); final View lineView = (View) findViewById(R.id.vwLine); final TextView tvTotalLabel = (TextView) findViewById(R.id.tvTotal); final TextView tvTotalAmountLabel = (TextView) findViewById(R.id.tvTotalAmount); final TextView tvNameLabel = (TextView) findViewById(R.id.tvName); final TextView tvTollLabel = (TextView) findViewById(R.id.tvToll); final RadioGroup rgTypeOfInf = (RadioGroup) findViewById(R.id.rgType); final RadioGroup rgTypeOfTrip = (RadioGroup) findViewById(R.id.rgTripType); </code></pre> <p>Originally everything was working fine until I moved some of the objects to a different layout which is no longer in <code>main</code> layout file and now my application FC when it's opening.</p> <p>The following are in a different layout, <code>result.xml</code>. Do I have to initialize them separately?</p> <pre><code>final EditText showLog = (EditText)findViewById(R.id.etShowLog); showLog.setFocusable(false); final Button btnClearWin = (Button) findViewById(R.id.btnClear); final Button btnSaveTrip = (Button) findViewById(R.id.btnSave); </code></pre> <p>When I comment out the above four lines, the application opens just fine.</p> <p>Logcat:</p> <pre><code>07-25 10:27:27.955: E/AndroidRuntime(13791): FATAL EXCEPTION: main 07-25 10:27:27.955: E/AndroidRuntime(13791): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.test.testing/com.test.testing.MainActivity}: java.lang.NullPointerException 07-25 10:27:27.955: E/AndroidRuntime(13791): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2306) 07-25 10:27:27.955: E/AndroidRuntime(13791): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2356) 07-25 10:27:27.955: E/AndroidRuntime(13791): at android.app.ActivityThread.access$600(ActivityThread.java:150) 07-25 10:27:27.955: E/AndroidRuntime(13791): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1244) 07-25 10:27:27.955: E/AndroidRuntime(13791): at android.os.Handler.dispatchMessage(Handler.java:99) 07-25 10:27:27.955: E/AndroidRuntime(13791): at android.os.Looper.loop(Looper.java:137) 07-25 10:27:27.955: E/AndroidRuntime(13791): at android.app.ActivityThread.main(ActivityThread.java:5195) 07-25 10:27:27.955: E/AndroidRuntime(13791): at java.lang.reflect.Method.invokeNative(Native Method) 07-25 10:27:27.955: E/AndroidRuntime(13791): at java.lang.reflect.Method.invoke(Method.java:511) 07-25 10:27:27.955: E/AndroidRuntime(13791): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795) 07-25 10:27:27.955: E/AndroidRuntime(13791): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:562) 07-25 10:27:27.955: E/AndroidRuntime(13791): at dalvik.system.NativeStart.main(Native Method) 07-25 10:27:27.955: E/AndroidRuntime(13791): Caused by: java.lang.NullPointerException 07-25 10:27:27.955: E/AndroidRuntime(13791): at com.test.testing.MainActivity.onCreate(MainActivity.java:51) 07-25 10:27:27.955: E/AndroidRuntime(13791): at android.app.Activity.performCreate(Activity.java:5104) 07-25 10:27:27.955: E/AndroidRuntime(13791): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1080) 07-25 10:27:27.955: E/AndroidRuntime(13791): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2260) 07-25 10:27:27.955: E/AndroidRuntime(13791): ... 11 more 07-25 10:27:27.963: W/ActivityManager(381): Force finishing activity com.test.testing/.MainActivity 07-25 10:27:28.517: W/ActivityManager(381): Activity pause timeout for ActivityRecord{4163fe28 u0 com.test.testing/.MainActivity} 07-25 10:27:28.666: I/qtaguid(381): Failed write_ctrl(s 0 10116) res=-1 errno=1 07-25 10:27:28.666: W/NetworkManagementSocketTagger(381): setKernelCountSet(10116, 0) failed with errno -1 07-25 10:27:38.666: W/ActivityManager(381): Activity destroy timeout for ActivityRecord{4163fe28 u0 com.test.testing/.MainActivity} 07-25 10:28:00.166: D/dalvikvm(2069): GC_CONCURRENT freed 3198K, 52% free 13534K/27904K, paused 3ms+3ms, total 29ms 07-25 10:28:00.166: D/dalvikvm(2069): WAIT_FOR_CONCURRENT_GC blocked 23ms </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSi8
    1. USSi8
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid App crashes due to adding a layout
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COWhat do you mean with "other than main"?
      singulars
      1. POAndroid App crashes due to adding a layout
      1. USWarpzit
    2. COplease post you logcat output as well
      singulars
      1. POAndroid App crashes due to adding a layout
      1. USEmil Adz
    3. COYou can initialize views that are in your layout xml that is set to the activity. if its in a different xml and you try to initialize you get NPE.
      singulars
      1. POAndroid App crashes due to adding a layout
      1. USRaghunandan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload