nn::fs::VerifySaveDataSecureValue Function

bool VerifySaveDataSecureValue(
     bit64 value
);

bool VerifySaveDataSecureValue(
     bit64 value,
     bit64 mask
);

For downloadable applications, gets the 64-bit value from the save region in CRT System Memory that was written there by the SetSaveDataSecureValue function, and compares this with value. The save region is unique to the application that called this function, so the same application always references the same save region.

If this function is called with the factory defaults or immediately after initializing the system, the values in the internal memory are treated as 0 for processing. Immediately after these initializations occur, the save data for the download application should be in an uninitialized state. If the save data is not initialized, do not make the assumption that the internal memory values are 0. Even when you have not performed any processing that corresponds to SetSaveDataSecureValue(0), such as downloading an application again, it is possible that the save data is in an uninitialized state. In short, do not call this function if the save data has not been initialized.

If the physical memory chips for a system were replaced to repair damage, or the system experienced corrupted internal memory data, the values in the internal memory are treated as 0 for processing, the same as for factory defaults. In these cases, because this function is called when the value is not 0, the function returns FALSE. In other words, the passed value is not valid. If you cannot allow save data to become unusable because of repairs of damage to the internal memory, call the VerifySaveDataSecureValueLoosely function instead.

When this function is called from a card application, it always returns TRUE.

For downloadable applications, gets the 64-bit value from the save region in CRT System Memory that was written by the SetSaveDataSecureValue function, and compares this with value. No comparison is made on bits that are not set in the mask argument. The save region is unique to the application that called this function, so the same application always references the same save region.

If this function is called with the factory defaults or immediately after initializing the system, the values in the internal memory are treated as 0 for processing. Immediately after these initializations occur, the save data for the download application should be in an uninitialized state. If the save data is not initialized, do not make the assumption that the internal memory values are 0. Even when you have not performed any processing that corresponds to SetSaveDataSecureValue(0), such as downloading an application again, it is possible that the save data is in an uninitialized state. In short, do not call this function if the save data has not been initialized.

If the physical memory chips for a system were replaced to repair damage, or the system experienced corrupted internal memory data, the values in the internal memory are treated as 0 for processing, the same as for factory defaults. In these cases, because this function is called when the value is not 0, the function returns FALSE. In other words, the passed value is not valid. If you cannot allow save data to become unusable because of repairs of damage to the internal memory, call the VerifySaveDataSecureValueLoosely function instead.

When this function is called from a card application, it always returns TRUE.