startActivity crashes if I do not open the activity from another path

Question

So I have 2 ways an activity can be opened. One is from the activity flow of:

Main > Tracks > Day > Topic > TrackSelect > TrackInfo

and the other is:

Main > MySchedule > TrackInfo

If I try to get TrackInfo to open up via the second path, it crashes the app.
However, If I go from the first path, then all the way back to the main, then through the second path, it works perfectly. Is there something weird going on?

AndroidManifest:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="fayko.conference_app">

<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<application
    android:allowBackup="true"
    android:icon="@mipmap/ic_launcher"
    android:label="Conference-App"
    android:supportsRtl="true"
    android:theme="@style/AppTheme">
    <activity
        android:name=".mainSelection"
        android:label="@string/app_name">
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />

            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>
    </activity>
    <activity
        android:name=".topicScreen"/>
    <activity
        android:name=".myScheduleScreen" />
    <activity android:name=".trackSelection" />
    <activity android:name=".mainScreen" />
    <activity android:name=".daySelection" />
    <activity android:name=".trackInfoScreen" />
    <activity android:name=".mapChoose" />
    <activity android:name=".sponsorScreen" />
    <activity android:name=".committeeScreen" />
    <activity android:name=".welcomeScreen"></activity>
</application>

</manifest>

Code from TrackSelect > Track Info :

Intent intent = new Intent(trackSelection.this,trackInfoScreen.class);
startActivity(intent);

Code from MySchedule > TrackInfo :

Intent intent = new Intent(myScheduleScreen.this,trackInfoScreen.class);
startActivity(intent);

I appreciate any help you guys can give me.

Answer 1

It turns out that the issue I was having was due to some internal code. Even thought he stacktrace was saying things about socket lost for the debugger.